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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuine value on the response side by enumerating what the payload contains (photos, delivery/payment, seller ratings), which is important because no output schema exists; it does not mention behavior for a bad or missing id.

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?

A single front-loaded sentence with no filler, and the most useful scoping information ('one listing') leads. It is efficient, though the colon-list style leaves the verb implicit rather than stating the action outright.

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 read tool with no output schema, the description does the heavy lifting by summarizing the returned fields, and annotations cover safety and idempotency. Minor gaps remain around missing-id behavior and pagination of large photo sets, but nothing essential to calling it correctly is absent.

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 single parameter has 100% schema description coverage, including its provenance ('Listing id from search_listings'), so the schema already carries the semantics. The description adds no format, range, or error-handling detail about the id beyond what the schema provides.

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 names a specific resource and scope ('Everything about one listing') and enumerates the content returned (description, photos, delivery and payment, seller ratings), which lets an agent distinguish it from search_listings as a detail fetch. It lacks an explicit verb ('get') and never names a sibling outright, so it falls short of a 5.

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?

There is no explicit statement of when to use this versus search_listings or get_category; usage is only implied by 'Everything about one listing' and by the schema note that the id comes from search_listings. The workflow is inferable (search first, then fetch details) but never stated.

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