Delete Project File

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

Annotations indicate destructiveHint=true, so the description's 'cannot be undone' aligns, but it also mentions 'moving to the recycle bin,' which implies potential recoverability. This internal contradiction undermines transparency. The description does not add other behavioral context like auth requirements or rate limits beyond annotations.

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 contains five sentences, but repeats 'cannot be undone' twice and redundantly states 'Permanently removes the specified Documents.' Could be more concise by dropping duplicates.

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?

The description covers the basic action and parameters but fails to resolve the recycle bin vs. permanent deletion ambiguity. It doesn't mention what happens to the file after moving to recycle bin or any side effects. Given no output schema, return value information is missing, but functionality is simple.

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 100%, and the description merely repeats 'Required parameters: id, project_id' without adding meaning beyond the schema's descriptions. Baseline 3 is appropriate as the schema does the heavy lifting.

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 tool deletes a file ('Delete the specified File'), but includes contradictory statements: moving to recycle bin vs. permanently deleting. The verb 'delete' and resource 'File' are clear, and the title aligns. However, the inconsistency reduces clarity slightly.

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?

No guidance on when to use this tool vs. alternatives like delete_project_folder or delete_project_file_version. The description only says 'Use this to permanently delete the specified Documents' without context or exclusions. Sibling tools are abundant but no differentiation.

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