Delete an upload

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

The description goes beyond the destructiveHint annotation by stating the deletion is irreversible, the file and its links stop working immediately, and errors such as not found, already deleted, or wrong owner surface as normal tool errors. This gives an agent useful behavioral expectations.

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 three sentences with the main action and consequence front-loaded. Every sentence contributes: what it does, how to get the id, and what error behavior to expect. There is no filler.

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 one-parameter destructive tool with output schema and annotations, this description is complete. It covers purpose, side effects, id provenance, and error behavior. An agent has everything needed to select and invoke it correctly.

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 `id` at 100% coverage, and the description adds retrieval guidance: use the response from upload_image right after uploading, or list_uploads if the id is no longer available. This is genuinely useful beyond the schema's parameter description.

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 opens with a specific action and resource: 'Permanently delete one of your YourImageShare uploads by `id`'. It clearly distinguishes itself from siblings by present itself as the deletion tool while upload_image/list_uploads are framed as id sources.

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?

It gives clear usage context: use when you intend a permanent deletion, and it explains how to obtain the id from upload_image or list_uploads. It doesn't explicitly state when not to use, but since the siblings are upload/list tools, there is no deletion alternative needing exclusion.

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