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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the metric names, but those are return-value details already covered by the output schema, so it contributes essentially no behavioral context beyond what structured fields provide.

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 compact sentence with the resource stated first and the metrics last; nothing is padded. It is efficiently front-loaded, though extremely terse at the cost of missing guidance.

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?

An output schema exists, so the description need not explain return values, and read-only semantics are covered by annotations. What remains missing is any hint about what the required 'id' refers to and when this tool is the right choice, which is a meaningful gap for a listing-oriented tool within a crowded sibling set.

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 0% and the single 'id' parameter has no description in the schema. The phrase 'a seller listing' faintly implies the id is a listing identifier, but the description never clarifies whether it expects a listing id, a seller id, or an internal tool id — a real ambiguity given siblings like get_tool, get_card, and get_result.

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?

Names the resource (per-listing stats for a seller listing) and enumerates the specific metrics returned (reads, attempted_use, confirmed_want), so the agent knows exactly what it retrieves. It does not, however, distinguish itself from adjacent siblings like listing_check or verify_my_listing, which also operate on listings.

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 whatsoever: no prerequisites, no indication of when to call this versus listing_check, verify_my_listing, or get_result. The agent must infer the trigger from the name alone.

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