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

Goes well beyond the annotations (destructiveHint/openWorldHint) by describing real consequences: public customer-visible action, words never lost on refusal (status 'manual_required'), Google moderation states pending/rejected_by_google with policy_violation detail. Annotations only flag non-idempotent/destructive; description supplies the operational meaning.

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?

Front-loads the action and its caution; information dense but long with digitated status details. Every sentence carries an operational consequence, though it could be tightened slightly.

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 destructive, open-world, non-idempotent mutation with no output schema, the description covers prerequisites, approval policy, failure fallback, and moderation outcomes — everything an agent needs to invoke it safely.

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 baseline 3; the description adds the crucial requirement that text must be the exact approved text and links review_id to list_reviews, giving modest extra guidance beyond the schema.

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?

States a specific verb (PUBLISH) and resource (a reply to this review's public Google profile), and it is clearly distinguishable from draft_reply by being the public, approved action.

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 says when to call: ONLY when the user has explicitly approved this exact text, one call per approved reply, never in bulk. It also explains what to do on refusal/rejection (manual fallback, write a different reply).

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