delete-data

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

Lacks disclosure of key behavioral traits like permanence, reversibility, or permission requirements. No annotations are present to compensate, leaving agents unaware of the destructive nature's implications.

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?

Single sentence with no redundant information, efficiently conveying the core action.

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?

Minimal context given the tool's destructive nature and lack of output schema. Does not explain return values, error handling, or idempotency, leaving gaps for agent decision-making.

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?

Adds value by clarifying enum choices for data_type with usage context ('Use 'documents' for text namespaces…'), beyond the schema's description. Schema coverage is 100%, so baseline is high.

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?

Clearly states delete action on specific data items within a namespace, distinguishing from sibling tools like delete-namespace which removes an entire namespace.

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?

Implies use for deleting specific items by ID but provides no explicit when-to-use or comparisons to alternatives, such as delete-namespace for bulk removal.

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