delete_file

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It clearly states the destructive nature and distinguishes two behaviors: move to trash or permanent deletion. It could add more context about irreversibility or permissions, but the core behavior is transparent.

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 and well-structured, with a front-loaded summary followed by a clear Args and Returns section. Every line provides useful information with no unnecessary fluff.

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 two-parameter tool, the description gives enough context to invoke it correctly: what it does, what the parameters mean, and what to expect back. The only notable gap is the absence of explicit warning about the irreversibility of permanent deletion and any permission requirements, which would be valuable for a destructive operation.

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 description coverage is 0%, and the description compensates by explaining both parameters: file_id is the ID of the file and permanent controls whether the deletion is permanent. It does not explicitly state the default behavior when permanent is false, but the parenthetical 'move to trash or permanent' and the schema default make this inferable.

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 states a specific verb and resource: 'Delete a file', and adds the important distinction between moving to trash and permanent deletion. This clearly differentiates it from sibling tools like list_files, download_file, and share_file.

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 purpose is clear enough that an agent can infer when to use it, but the description provides no explicit guidance about conditions, prerequisites, or when not to use it. No alternative deletion tool exists among siblings, so the lack of alternatives is not critical, but the guidance is still implicit rather than explicit.

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