Delete Image

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates state. The description adds the library scope and confirms deletion, but does not go beyond annotations to disclose side effects or irreversibility. Since annotations carry the safety profile, a mid score is appropriate.

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?

One short sentence that leads with the verb and object and contains no filler. It is appropriately minimal for a simple delete operation.

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 rich annotations (destructive, idempotent) and a fully documented schema, the description is sufficient for an agent to invoke the tool correctly. No output schema exists, but the description need not explain return values given the simplicity of the action.

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 fully describes asset_id as 'The asset ID of the image to delete' (100% coverage), so the description need not restate it. The description adds no parameter-level meaning beyond the schema, earning the baseline score of 3.

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 ('delete') and a specific resource ('an image from your AltText.ai library'), making the operation unambiguous. It clearly distinguishes this from sibling operations like update_image or list_images by naming the exact action and scope.

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 makes the intended use obvious: call this when an image should be removed from the AltText.ai library. It does not explicitly name alternatives or exclusions, but for a single-purpose destructive action against siblings like update_image, the context is clear enough.

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