Delete from Hydra DB

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description adds the irreversible nature of the action, which is a key behavioral trait. However, it lacks details on side effects, error handling, or authorization requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences are concise and front-loaded with the action. Every sentence adds value: action description and irreversibility hint. No redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should explain return behavior or confirmation. It only states the action and irreversibility, omitting what happens on success/failure or if the item doesn't exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% via descriptions, and the description adds no additional meaning beyond the schema for parameters 'id' and 'kind'. It does not provide formatting or usage tips beyond what's in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Delete a memory or knowledge source from Hydra DB by its ID,' with a specific verb and resource. It implicitly distinguishes from sibling 'hydra_db_delete_memory' by mentioning 'kind' to select family, but does not explicitly differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description warns 'This action is irreversible' but provides no guidance on when to use this tool versus alternatives (e.g., hydra_db_delete_memory). No context on prerequisites or conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.