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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: it reports cache freshness and an actionable recommendation, and 'Never contacts Google' clarifies that resolution is local even though the input is a Google Maps URL — a real concern the annotations only hint at.

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 imperative 'Call first,' then the capability, then the recommendation branches. Dense and nearly waste-free; the parenthetical about corroboration is slightly compressed but still earns its place by altering the recommended action.

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?

There is no output schema, and the description compensates by explaining what is returned: cache existence, freshness, and a recommendation. Combined with the fully documented parameters, an agent has what it needs to call this correctly; only the zero-argument case is left unspecified.

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 both url and place_id are already documented in the schema, including the short-link caveat. The description repeats the 'link or place_id' framing without adding format or precedence details. Notably it does not say what happens when neither argument is supplied even though none are required, leaving that ambiguity unaddressed.

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 and resource: resolves a Google Maps link or place_id and reports cache status, freshness, and a recommended next action. This is clearly distinguishable from siblings like get_place_trust (which presumably returns the trust result itself) and list_scored_places (which enumerates).

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?

The opening 'Call first' gives explicit ordering guidance, and the description routes the agent to one of two follow-ups: use the cached result or collect/submit reviews. It also carves out the corroboration case for single-source cached results. It stops short of naming which sibling to call for each branch, so the mapping is inferred rather than stated.

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