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

Annotations already declare readOnly/destructive=false and openWorld=false, so the safety bar is partly met; the description adds two non-obvious behaviors: iOS clients may flag the feature off yet the tool still works, and it is read-only with no Firestore writes. It stops short of describing latency, cost, or whether results are cached.

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 dense paragraph with no filler: purpose, exclusion, platform caveat, invocation forms, return fields, and safety note, in roughly that order of importance. Every clause carries information.

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 usefully enumerates the return fields (reviews_found, msrp, general_consensus, summary, overall_rating, reviewers), and no parameters are required, which is consistent with the three alternative invocation paths described. Minor gap: it doesn't state what happens when resolution fails or finds no reviews.

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 per the rubric the baseline is 3. The description goes beyond the schema's per-field text by spelling out the legal parameter combinations and the resolution behavior (bottleId limited to own collection; username/userId + bottleId resolves a display name first), which the schema does not express as a whole.

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?

"AI community-review research for a bottle" gives a specific verb (research) and resource (bottle reviews), and the parenthetical confirms the underlying operation name. It also distinguishes itself from a class of siblings by stating "Not a user tasting-note form," though it doesn't name the specific alternatives (e.g., get_expression, lookup_bottle).

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 description sketches three invocation forms (bottleName, bottleId, or username/userId + bottleId) and gives one exclusion (not a tasting-note form), so usage is implied but not fully resolved. It never says when to prefer this over lookup_bottle or get_user_bottle, which an agent selecting among ~45 siblings would need.

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