⚠️ Reply to a review

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

Disclosure that answer is public after moderation and requires user confirmation adds significant context beyond annotations. No contradiction with readOnlyHint=false and destructiveHint=true.

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?

Compact but complete: purpose, warning, requirements, returns, user instruction, and sibling link. No filler sentences.

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?

Given 4 parameters, no output schema, and annotations, the description covers purpose, required params, side effects (public, moderation), prerequisite (reviewId), return value, and alternative action. Highly informative.

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?

Description explains that reviewId comes from reviews_get_reviews_v1 and message must not be empty. Schema coverage is 100%, but description adds cross-reference and prudence. Dry run and idempotency key behavior also described.

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?

Clearly states verb 'Publishes' and resource 'seller answer to a review'. Distinguishes from sibling tool 'reviews_remove_review_answer_v1' by mentioning deletion as alternative.

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?

Explicitly instructs to confirm with user, specifies required arguments (reviewId, message), warns about public visibility and moderation, and provides alternative for deletion. Context for when to use is clear.

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