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

No annotations are provided, so the description carries the burden. It does usefully disclose that the payload includes rating and latest reviews, but says nothing about permissions, behavior on an invalid or unknown UUID, or pagination limits on 'latest reviews'.

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 short sentence, front-loaded with the primary purpose and finished with the notable return contents. No filler or redundant restatement of the name.

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 single-parameter read tool with a fully documented schema and no output schema, this is nearly sufficient: the description tells the agent what comes back. Only the absence of error/failure behavior keeps it from being 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?

Schema coverage is 100% — listing_id is typed as string with 'UUID' documented — so the schema does the heavy lifting. The description adds no meaning beyond that, never mentioning the identifier, so baseline 3 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?

States a specific verb (implicitly 'get') and resource ('one listing') plus what the response contains (rating, latest reviews). It distinguishes itself from search_listings by scoping to a single listing, though it never names that sibling explicitly.

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: the required listing_id makes clear it's a lookup-by-ID tool, so an agent can infer it needs an ID already in hand. There is no explicit when-to-use, no when-not-to-use, and no pointer to alternatives like search_listings for discovery.

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