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

Beyond the annotations (idempotent, non-destructive, closed-world), the description discloses the purchase-eligibility prerequisite and that calling it again overwrites an existing review rather than creating a duplicate — the key behavioral fact for an agent. It omits moderation/publish timing and what is returned, which is a modest gap.

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 that front-loads the create case and appends the update case. No filler, no repetition of schema or annotations.

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?

There is no output schema, so return values need not be explained, but the nested input object with seven optional numeric/string review fields is a substantial surface the description never touches. Adequate for the create/update intent, insufficient for an agent deciding which fields to populate.

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 50%, with only `rating` and `context` documented. The description says nothing about the nested optional fields — body, title, design, updates, performance, code_quality, documentation — so the whole sub-score model is left entirely to the schema with no guidance on which apply to which listing type.

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 gives a specific verb and resource ("Reviews a listing") and additionally covers the edit case ("or changes their review of it"). It is clearly distinct from siblings like reply_to_review, but it does not explicitly name that distinction.

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 a real precondition — the actor must have bought the listing — which tells an agent when the call is valid. It does not say what to do when the user has not purchased, nor does it route to the more appropriate sibling for responding to an existing review.

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