Delete File

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

The description adds 'This action is permanent,' which conveys irreversibility beyond the destructiveHint annotation. It does not describe cascading effects or required permissions, but for a simple delete operation the added warning is meaningful.

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?

Two short sentences with the core action front-loaded. No filler or redundancy; the important permanence warning is included without bloat.

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 single-parameter destructive action, the description adequately equips an agent: it identifies the target, the required identifier, and the permanence of the action. It does not describe response behavior or side effects, but these are not critical for a basic delete tool.

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 already documents 'file_id' with its type and meaning, and the description simply refers to 'a file by ID,' adding no deeper semantic detail. The schema carries the parameter documentation, so the description adds little beyond confirming the ID is used.

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 a specific verb+resource construction, 'Delete a file by ID,' which plainly states what the tool does. It is clearly distinguishable from sibling delete tools like delete_assignment or delete_discussion because it is specific to files.

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 provides no guidance on when to use this tool versus alternatives, such as update or list operations. While the intent is inferable, it does not state exclusions or conditions for use.

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