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

Discloses irreversibility, that run outputs persist, and that bytes and parsed contents are gone—detail beyond the destructiveHint annotation. This gives an agent a precise model of side effects without contradicting 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?

Three sentences with the core purpose and consequential side effects front-loaded. No filler; every clause contributes useful 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?

The description, schema, output schema, and annotations together cover what the tool does, when to use it, and its irreversible side effects. Nothing an agent needs to call it correctly is missing.

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 100%, so the description is not required to add parameter-level detail. It adds no extra semantics beyond the schema, which meets the baseline for high coverage.

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?

Clearly states the action (permanently delete) and the resource (uploaded file from Extend files group). It distinguishes from sibling delete tools by explicitly targeting a file rather than runs, webhooks, or other resources.

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?

Provides clear context that processed runs keep their outputs while the file's bytes and parsed contents are removed, helping an agent understand consequences. It does not explicitly name alternatives, but the file scope and deletion semantics make the appropriate use case unambiguous.

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