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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds concrete meaning: repeats never duplicate reviews and never fire alerts. That 'no alerts' detail is behavioral context an agent could not infer from the annotations alone, which is exactly the kind of value a description should add.

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 compact sentences with zero filler; the action and the timing rationale are front-loaded, and the safety note follows naturally.

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 simple two-parameter import with annotations covering safety and no output schema, the definition covers what the agent needs to decide and act. It does not say what the call returns or whether it consumes quota, which is a minor gap rather than a blocking one.

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% and both parameters are documented in the schema, so the baseline is 3. The phrase 'the site's location' slightly clarifies how site_id maps to a Google Business Profile location, but no format or constraint detail is added 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?

The description states a specific verb and resource: 'Import the latest Google reviews for the site's location.' It is distinguishable from the read-only sibling list_google_reviews because it is explicitly an on-demand import, though it never names that sibling to sharpen the contrast.

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?

'now (otherwise they refresh about hourly)' gives a clear trigger condition: call this when the agent needs fresh reviews immediately rather than waiting for the automatic hourly refresh. It stops short of naming alternatives or stating when not to call it.

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