delete_download

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

The description states it deletes from disk and registry, implying destructiveness, but provides no details on side effects (e.g., whether it's permanent, if permissions are needed, or error handling). With no annotations, more transparency is needed.

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 a single short sentence, no wasted words. However, it lacks structure such as usage notes or examples, which would further improve clarity.

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 is minimal and does not address return values, errors, or expected behavior beyond deletion. For a destructive tool, the agent likely needs to know if it succeeds silently or throws errors, which 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?

The input schema descriptions already fully explain the parameters (downloadId and userId), so the description adds no extra meaning. Baseline score of 3 is appropriate given 100% schema 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?

The description clearly states the action ('Delete'), the resource ('a downloaded file'), and the scope ('from disk and registry'), making it easy to understand what the tool does. It distinguishes from siblings like 'get_download' and 'list_downloads' by the destructive nature.

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 versus alternatives, nor any prerequisites or context for safe use. For example, it does not mention checking if the download exists or that deletion is irreversible.

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