delete_image

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action (delete) and the input (path) but does not disclose that deletion is likely permanent and irreversible, whether special permissions are required, or what happens if the path does not exist. This is a significant transparency gap for a destructive tool.

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, concise sentence that contains no filler or irrelevant information. It is front-loaded with the action and resource, making it easy to process quickly.

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 tool is simple (one parameter, no output schema), so the description is mostly adequate. However, it omits important operational context such as whether the deletion is permanent and whether errors are raised for non-existent paths. Given the lack of annotations, a bit more detail would make it complete.

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 already describes 'path' as 'Absolute path to the image file to delete' with 100% coverage, so the description adds no additional semantic meaning. The baseline of 3 applies because the schema handles the parameter documentation adequately.

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'), identifies a precise resource ('image file'), and clearly scopes the action to a single file identified 'by path'. This differentiates it from sibling tools like 'cleanup' which likely handle bulk deletion, and from 'view_image'/'list_images' which are read operations.

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 implies the tool is for deleting a specific image when you have its path, but it does not explicitly state when to use this versus alternatives like 'cleanup' for bulk deletion, nor does it mention prerequisites like locating the path via 'list_images'. The guidance is implied rather than explicit.

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