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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds some value by noting the response includes original text plus structured fields, but with no output schema it should say more about the actual return shape.

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 efficient sentence with no filler. It is front-loaded on the returned content, though it is thin enough that it could carry a bit more without becoming bloated.

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?

This is a simple read tool and annotations cover its safety profile, but with no output schema the description is the only source of return-value detail and gives just one clause about it. Adequate for a minimal fetch-by-ID tool, but leaves gaps around the response structure.

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 description coverage is only 50%: language is documented in the schema (with an enum and default), but listing_id is undocumented in both schema and description. The phrase "in the requested language" loosely ties to the language parameter but adds no syntax beyond the enum, so the description only partially compensates.

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 characterizes the returned object ("a full listing ... with the original text and structured fields") but never states the action verb explicitly, and it does not distinguish the tool from siblings like search_listings or get_author. The name/title carry the "get" semantics, leaving the description somewhat vague on what it does.

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 when-to-use guidance, no prerequisites, and no mention of the alternatives (search_listings for discovery, get_author for related data). An agent must infer that this fetches a single listing by ID.

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