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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: URLs are not fetched (important for an agent expecting fetching to happen), and names/URLs are candidate clues rather than verified identity — a reliability caveat the annotations cannot express.

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?

Three tight sentences with no filler; the invocation form is front-loaded and the caveats are ordered after it. Slightly compressed to the point of ambiguity, but nothing is wasted.

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 while the description sketches returns ('original reviews, matching context, coverage and next action'), it is thin for a tool whose only structured input is a twenty-field nested identifier object with zero field descriptions. The complexity of the target object is simply unaddressed.

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 0%, so the description carries the full burden. It does explain q (name or public provider URL) and gestures at 'target identifiers,' which is useful, but limit is never mentioned and the nested target object's twenty identifier fields (gtin, seller_id, listing_id, store_url, etc.) are entirely unexplained in both schema and description.

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 verb phrase is 'start a public lookup,' which is soft, and the resource is left implicit — the name says 'experiences' but the description says it returns 'original reviews.' It lists the inputs (q name/URL or target identifiers) and the return shape, but never distinguishes itself from siblings like find_reviews or resolve_review_target, so an agent can't confidently pick it without reading schemas.

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?

It tells you how to invoke it (q vs target identifiers) but not when to use it versus find_reviews, find_merchants, find_offerings, or resolve_review_target. There is no stated precondition, no exclusion, and no routing guidance among a large sibling set.

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