delete_file

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

Fully discloses destructive nature, different behavior for KB vs project files, non-idempotency, no external auth/rate limits, and return value. Since annotations are absent, the description carries this burden well.

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?

Front-loaded with 'DESTRUCTIVE.', every sentence provides unique value, no redundant information.

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 single parameter, no output schema, the description covers all necessary aspects: behavior, consequences, alternatives, return value, and error conditions.

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 covers the id parameter thoroughly (100% coverage). The description doesn't add much beyond schema for this parameter but implies existence requirement, so baseline with slight bonus.

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 the action ('permanently delete one file by ID') and distinguishes from sibling tools by mentioning the bulk variant and alternatives like remove_tags and set_favorite.

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?

Explicitly states when to use ('only when the file is truly obsolete') and alternatives ('deprioritise without losing data, untag or unfavorite'), plus non-idempotency and error behavior.

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