documents_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the document is moved to trash, implying non-destructive deletion, but does not mention any permissions required, whether the trash is recoverable, or what happens to the document after being trashed. No annotation contradicts the description.

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?

The description is a single, concise sentence that directly states the action. No wasted words, and the essential information is front-loaded.

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?

For a simple delete tool with one well-documented parameter, the description is minimally adequate. However, with no annotations and no output schema, it does not clarify side effects (e.g., whether trash is reversible, retention policies) or distinguish itself from related tools. It is more complete than a tautology but still leaves gaps.

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?

The schema fully documents the single parameter 'id' as 'Document ID' (100% coverage), so the description adds no additional parameter meaning. The baseline of 3 applies because the schema already handles parameter documentation adequately.

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 uses the specific verb 'Move' and the resource 'document to trash', clearly distinguishing this delete operation from sibling tools like documents_move (which moves to a new location) and documents_archive (which archives without trashing). The action is unambiguous.

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 implies this is the deletion tool by naming the trash destination, but it does not explicitly state when to use this versus alternatives like documents_archive or documents_move. It provides no exclusion criteria or alternative recommendations, though the phrase 'move to trash' implies a soft-delete behavior.

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