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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies a read operation ('Retrieve') and discloses nothing about pagination (limit/offset defaults), rate limits, or result shape. For a tool wrapping 12 distinct operations, this is a substantial transparency gap.

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?

A single short sentence that is front-loaded and free of filler. It is efficient, though its brevity is a symptom of under-specification rather than disciplined scoping.

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 an output schema present, return values need not be explained, but a tool exposing 12 operations and a deep nested payload demands far more than one sentence. Nothing tells the agent how the operation enum, filters, or platform targeting interact, leaving the definition materially incomplete.

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 0%, so the description is expected to compensate for the very complex nested payload, but it adds nothing about operation, filters, targets, platform, or language semantics. The only partial relief comes from a handful of inline schema descriptions (operation, target, keyword, language, location), not from the description text.

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 gives a clear verb ('Retrieve') and enumerates the resource domains (local business, hotel, review, reputation data), which an agent can map to the four operation families in the enum. It is clear on its own but does no explicit sibling differentiation (e.g., vs. social-google-maps-search or competitor-data), so it falls short of a 5.

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?

There is no when-to-use guidance, no mention of the 12 available operations, and no alternatives named. An agent cannot tell from the description which operation to select or when to prefer this tool over a sibling.

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