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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds behavioral context the annotations don't: default ordering puts unanswered reviews first, and it discloses the review id as the handoff key to propose_review_reply. It doesn't state pagination behavior beyond the limit param.

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-loaded with the operation, ordering, and fields before any secondary guidance. The final two sentences about reply tone belong more naturally on propose_review_reply and are slightly tangential to a list tool, though they don't obscure the core description.

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?

With no output schema, the description usefully enumerates the return fields and ordering, and the limited 2-param surface is fully documented by the schema. Complete enough to call correctly; pagination and total-count behavior remain unspecified but are minor here.

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 100%, so both params (limit, only_unanswered) are already documented in the schema and the baseline is 3. The description's 'unanswered listed first by default' complements only_unanswered's default=true, but adds no syntax or format detail beyond that.

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+resource ('List the owner's Google reviews') and enumerates returned fields (id, star rating, text, existing reply) plus ordering (newest first, unanswered first). An agent can distinguish it from siblings like my_photos, my_posts without opening a schema.

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 routes the agent forward: 'Use a review id with propose_review_reply.' That names the alternative tool and the handoff condition, though it doesn't say when NOT to use this tool or what other review-related paths exist.

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