hive

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

24/24 tools missing one or more hints — vault_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vault_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vault_ask (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +21 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

2 tools perform destructive updates without destructiveHint — vault_delete deletes at line 696 (filepath.unlink()); vault_delete deletes at line 696 (filepath.unlink())

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

2 tools describe read intent but their handlers mutate — vault_patch (line 540: filepath.write_text(working, encoding="utf-8")); vault_patch (line 540: filepath.write_text(working, encoding="utf-8"))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool handlers catch errors

20/24 tool handlers wrap calls in try/catch (83%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

vault_patch: description implies read-only but handler writes/deletes/executes; vault_patch: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.