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

Annotations already cover the safety profile (readOnly, idempotent, not destructive, closed-world), so the description correctly focuses on what annotations cannot say: no credentials required, the next_cursor/after pagination loop with identical filters, and that text is untrusted. The untrusted-content warning and citation guidance are genuinely useful behavioral context beyond the annotations.

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?

Four dense sentences, front-loaded with the core purpose and scoping, then pagination, then trust/citation rules. Every sentence carries information, though the pagination sentence is somewhat run-on.

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 helpfully names return fields (source_url, evidence_basis, next_cursor) and explains the pagination contract, which is what an agent needs to iterate correctly. Minor gap: it does not mention the limit ceiling of 50, though the schema already enforces it.

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 must carry the parameter burden, and it largely does: q is explained as merchant/product name and feedback search, the merchant_id/offering_id/evidence_basis filters are named, and 'after' is tied to the next_cursor pagination loop. Only 'limit' is left unaddressed, and evidence_basis semantics beyond its enum are not expanded.

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 ('Browse') and resource ('published consumer experiences'), and explicitly distinguishes itself from sibling get_reputation by noting 'latest-100 reputation summaries do not cover the full directory'. An agent can tell this apart from get_review (single) and get_reputation (summaries) without opening any schema.

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?

Gives clear context for use — public directory browsing without credentials, and the condition that selects it over reputation summaries. It does not explicitly name get_review as the alternative for a single record, so the when-not guidance is partial but the routing intent is unambiguous.

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