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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds the auth requirement and enumerates returned sections, which is modest added value, but discloses nothing beyond annotations and the output schema about rate limits or failure modes.

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?

Two short sentences, front-loaded with the resource and scope, then the auth requirement. Every clause earns its place, though it could be trimmed slightly given the output schema already lists the returned fields.

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?

With annotations covering safety, a 100%-covered schema, and an existing output schema, the description supplies the one thing not in structured fields (the manage-token requirement and seller-perspective scope). Complete enough to invoke correctly; only the missing sibling routing keeps it from a 5.

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 100%, so both domain and manageToken are already documented, including the bearer-token warning. The description restates the token requirement but adds no formatting or syntax detail beyond the schema. 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?

The description states a specific verb and resource ('a seller's own view of one listing') and enumerates the content returned, which distinguishes it from the buyer-facing siblings like read_for_sale_page. It does not name a sibling explicitly, but the 'seller's own view' framing is discriminating enough for an agent to pick the right tool.

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?

It states the prerequisite ('Needs the manage token'), which is real usage guidance, but offers no explicit when-to-use vs when-to-use-something-else, e.g. versus read_for_sale_page or read_for_sale_dns. Usage is implied by the seller-perspective framing rather than spelled out.

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