delete_file

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

With no annotations, the description carries full burden. It discloses that the tool is destructive ('delete', 'Use carefully'), but lacks details on reversibility, permissions required, or side effects. The output schema exists but the description does not clarify behavioral aspects beyond deletion.

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 very short (two sentences) and front-loaded with the core action. The second sentence 'Use carefully' adds a warning but is minimal. Overall concise, though the warning could be more specific.

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?

Despite having an output schema, the description omits important context such as whether this action is irreversible, if it requires specific permissions, or what happens to related entities. For a destructive tool with no annotations, more context is needed to ensure safe and correct usage.

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 0%, meaning no descriptions in the input schema. The description does not add any meaning to the 'order_id' parameter beyond the parameter name itself. The agent gains no additional understanding of what values are valid or how to format the id.

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 verb 'delete' and the resource 'all files associated with an order_id'. It distinguishes from sibling tools like 'rename_file' and 'get_file_detail', though it could explicitly note that it deletes multiple files at once.

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?

Only a generic warning 'Use carefully' is provided. No explicit guidance on when to use this tool versus alternatives, prerequisites, or conditions that should be checked before invocation. Sibling tools like 'delete_custom_vocabulary' and 'delete_webhook' are distinct, but the description does not help an agent decide if this is the correct action.

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