conversations_send_review_reply

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds no additional behavioral context (e.g., that it posts publicly, may overwrite existing replies, or requires specific permissions). For a write operation targeting an external system (Google My Business), this lack of detail is a gap, though not a contradiction.

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 a single, concise sentence with no fluff. It is front-loaded with the core action and target, making it easy to parse. No unnecessary words or repetitive information.

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 tool with three parameters, all documented in the schema, the description is adequate but incomplete. It doesn't mention potential side effects, error conditions, or when it should not be used (e.g., only for conversations tied to Google My Business reviews). The schema fills some gaps, but the lack of behavioral context lowers completeness.

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 each parameter having descriptive text (e.g., conversationId 'must have reviewId', locationId defaults to GHL_LOCATION_ID). The description adds no extra meaning to parameters, so it relies entirely on the schema, which is adequate but not enhanced by the description.

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 ('Send') and resource ('review reply') with a clear target ('Google My Business'). It is unambiguous and distinguishable from other conversation tools by the 'Google My Business' qualifier, though it doesn't explicitly differentiate from conversations_send_a_new_message or similar tools without requiring inference from the name.

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 description provides no guidance on when to use this tool versus alternatives like conversations_send_a_new_message or other review-related tools. It lacks any conditions, exclusions, or references to sibling tools, leaving the agent to infer usage context.

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