delete_image

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

With no annotations provided, the description must carry the behavioral disclosure burden. It states that deletion is committed and that the tool is disabled in read-only mode, providing some context. However, it does not disclose whether deletion is permanent, whether specific permissions are required, or what side effects occur on the store listing.

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 exceptionally concise: two short sentences that immediately convey the action, scope, and an important runtime constraint. Every word earns its place, with no filler or redundancy.

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?

Given the rich input schema, the presence of an output schema, and the clarity of the deletion action, the description covers the essential context. It mentions the single-image scope, the commit behavior, and the read-only restriction. It could additionally mention irreversibility or required permissions, but the schema and output schema fill many gaps.

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 has 100% coverage with descriptive parameter details for all four required fields. The description adds only the notion of 'single store-listing image by ID', which slightly reinforces the image_id semantics but does not add meaning beyond the schema's own descriptions.

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' with a clear resource: 'a single store-listing image by ID'. It also distinguishes itself from the sibling tool 'delete_all_images' by emphasizing 'single' and 'by ID', making the tool's scope unambiguous.

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 clearly indicates this tool is for deleting one specific image (via ID) and notes it is 'Disabled in read-only mode', which is a useful exclusion. However, it does not explicitly mention alternatives like 'delete_all_images' or contrast with 'upload_image' or 'list_images', leaving the when-not guidance implicit.

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