List Google Business reviews

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

Annotations already provide readOnlyHint=true and destructiveHint=false. Description adds context about the connection between user and location defaults, but does not disclose additional traits like pagination or rate limits. No contradiction with annotations.

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?

Two sentences, front-loaded with main purpose, no wasted words. Perfectly concise and structured.

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?

Output schema exists, so return values are covered. Description covers core usage and defaults, but lacks mention of pagination or ordering constraints. Adequate for a read-only list tool with output schema.

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 60%. Description adds meaning for 'user' (profile name) and 'location_id' (defaults to account's location), but does not explain 'orderBy', 'pageSize', or 'pageToken' beyond the schema. Partially compensates for coverage gap.

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 clearly states the tool lists reviews for a Google Business Profile location, using specific verb 'List' and resource 'reviews for a Google Business Profile location'. It distinguishes from siblings like reply_to_google_business_review (write) and get_google_business_locations (list locations).

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?

Implies usage context: requires a Google Business profile that owns the connected account, and location_id defaults. No explicit guidance on when to use alternatives like reply_to_google_business_review for writing reviews or get_google_business_locations for listing profiles.

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