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

Goes well beyond the annotations by disclosing hard limits (max 6 items, question 8–140 chars, answer 2–600), the moderation rule that link-containing or mostly rewritten answers on live listings wait for review, and the required write scope. The 'empty list removes them' note is the kind of consequence an agent needs before invoking a replace operation.

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?

Three compact sentences ordered by importance: what it does, the input constraints and removal case, then the moderation and permission caveats. No filler and nothing buried.

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 return values need no explanation; the description instead spends its budget on the constraints, moderation delay, and auth that an agent cannot infer from structured fields. Complete for a replace-style mutation with only two parameters.

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%, so the baseline is 3, but the description adds minimum lengths (8 for questions, 2 for answers) that the schema only expresses as maxLength, plus the cardinality cap of 6 and the empty-list semantics. Only the productId parameter goes unelaborated, which is trivial.

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 a specific verb and resource ('Replace a listing's quick answers') and immediately defines the concept in parentheses as buyer questions answered by the maker, which separates it from the broad update_listing sibling.

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?

Establishes the replacement semantics ('the full list replaces the old one') and the removal path ('An empty list removes them'), plus the listings:write prerequisite. It does not explicitly contrast with update_listing or say when a maker should prefer this over editing the listing generally, so it stops short of full when/when-not guidance.

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