Remove a photo from a listing

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower; the description still adds ownership restriction ('your own listings') and the API-key prerequisite, which annotations do not carry. It stops short of saying whether the photo_url must currently exist in photo_urls or what happens on a mismatch.

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 sentence, front-loaded with the action and resource, with the two constraints (exact URL, own listing) and the auth note packed in without waste. Nothing to trim.

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 destructive tool with no output schema, the description covers scope, identifier source, ownership and auth. Minor gaps remain around failure behavior (unknown URL, last remaining photo) that would matter for a delete operation.

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 50%: photo_url is documented in-schema and the description reinforces it as an exact URL match against photo_urls. listing_id has no schema description and the description only indirectly constrains it via 'your own listings', leaving the lst_ prefix and ownership requirement mostly to the schema pattern.

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?

States a specific verb (Delete) and a narrowly scoped resource (one photo from one of your own listings), plus the identifier form (exact URL from photo_urls). This is clearly distinct from sibling add_listing_photo and from listing-level mutations such as delist_listing or update_listing.

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?

Usage is only implied: 'from one of your own listings' signals the ownership precondition, and GLONGUS_API_KEY signals the auth requirement. No explicit when-not-to-use or named alternatives (e.g. add_listing_photo, update_listing) are given, so the agent must infer the routing itself.

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