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

The description discloses a key behavioral rule beyond the annotations: only one response is allowed per review, and subsequent attempts return already_responded. This is valuable runtime nuance that the annotation block does not provide, even though it does not discuss auth requirements or other side effects.

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?

The description is two short sentences with no filler. The primary purpose is front-loaded, and the behavioral constraint is delivered in a compact, immediately useful way.

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 simple two-parameter mutation with no output schema, the description covers the core action, the uniqueness constraint, and the error condition. It lacks explicit alternatives or success-response details, but these are not critical for an agent to invoke the tool correctly in most cases.

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%, with both review_id and text already well-described in the input schema. The description's 'One response per review' statement reinforces the review_id constraint but does not add meaningful new parameter-level meaning beyond what the schema already states.

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 clearly states the action ('Post the seller's response to a review') and the specific resource (a review), making the tool's purpose immediately understandable. It also adds a unique constraint ('One response per review') that helps distinguish it from generic review actions, though it does not explicitly name or contrast sibling tools.

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?

The usage context is implied by the tool name and description: this is the tool for posting a seller's response to a review. However, it does not explicitly state when to prefer this tool over related siblings like seller_list_reviews or disputes_respond, nor does it mention exclusions or prerequisites.

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