delete_document

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

With no annotations provided, the description fully bears the transparency burden. It clearly states the action is irreversible and deletes associated data. However, it does not mention required permissions or ownership, which would be helpful for a destructive tool.

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 concise: a one-sentence purpose, a clear warning, and structured Args/Returns. No unnecessary words, and the most important information (irreversibility) 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?

Given the single parameter and the tool's simplicity, the description is complete. It covers purpose, irreversibility, parameter semantics, and return format (Dict with status and message). No gaps remain.

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 has 0% description coverage, but the description explicitly defines 'doc_id' as 'L'ID du document à supprimer', adding critical context beyond the plain schema type. The single parameter is well-explained.

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 it deletes a document and explicitly warns that the action is irreversible and removes all associated data. The name 'delete_document' is unambiguous, and the description distinguishes it from sibling tools like 'delete_column' or 'delete_workspace'.

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 usage via the name and warning, but lacks explicit guidance on when to use this tool versus alternatives such as 'move_document' or 'modify_document'. No when-not or exclusion criteria are provided.

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