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

"It's gone at once" discloses that the deletion is immediate with no undo or staging step, and "Needs listings:write" discloses the authorization requirement — both are behavior beyond what the annotations convey (annotations only say readOnly=false, openWorld=false, idempotent=false). The description does not mention that the effect is scoped to a single photo rather than the listing resource, which is why destructiveHint=false is best read as 'the listing survives'; there is tension with the irreversibility language but not a direct contradiction.

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?

Three short sentences with the action and scope front-loaded, followed by the effect and then the permission requirement. Every sentence carries distinct information — verb/resource, irreversibility, auth — with 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 two-parameter mutation with an output schema and full annotation coverage, the description supplies what matters: what is deleted, immediacy, and the required scope. Minor gaps remain around side effects on gallery ordering or cover designation, but nothing essential to a correct call 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?

Schema coverage is 100% and the schema already documents both productId and photoId, including that the photo id comes from get_my_listing. The description restates that ID provenance but adds no new format, constraints, or edge cases (e.g., whether photoId must belong to productId), so the baseline applies.

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?

Specific verb and resource with explicit scope: "Remove one photo from a listing's gallery." The 'one photo' scoping and 'by its id' qualifier make clear this deletes a single image rather than the whole listing or gallery, which implicitly separates it from add_listing_image and set_listing_cover. It stops short of naming a sibling outright, so it lands just below the top mark.

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 points the agent at get_my_listing as the source of the photoId and states the required scope listings:write, which is real usage context. However, there is no 'when not to use' guidance — e.g., whether a cover photo can be removed, or whether update_listing/listings edit should be used instead when reordering is the goal.

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