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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's marginal value is the cache-miss behavior, which it discloses plainly. It adds no auth, rate-limit, or staleness/TTL detail for a cache-backed tool, which is the main remaining 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?

Front-loaded with the purpose, then a dense enumeration of return fields, then the cache constraint. The field list is long but justified because there is no output schema; the single-sentence run-on is the only structural weakness.

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 does the heavy lifting by listing the returned artifacts (verdict, grade, trust score, adjusted rating, injection stats, duplicates, red flags, provenance), which is enough to decide whether to call it. Some items like 'reviewer-mix tiers' remain underspecified in shape, and cache-expiry behavior is unstated.

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 the url/place_id descriptions already explain the formats and that short-links cannot be resolved, so the description need not repeat them. It contributes nothing parameter-specific beyond 'a place', which is the expected baseline when the schema does the work.

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: it returns the cached fraud analysis for a place, and it enumerates the verdict taxonomy (looks_legit / not_sure / past_manipulation / inflated / manipulated). The 'Cache only' clause plus the check_place pointer cleanly separates it from the sibling check_place pipeline.

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 names the alternative and the condition that selects it: use this for cached lookups, and on a miss 'collect and submit the reviews (see check_place)'. An agent knows exactly what to do on an empty result without guessing.

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