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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely useful behavioral context: only 'latest published' reviews are returned, ratings are 'evidence-separated', and excerpts are explicitly not consensus or recommendations, which shapes how an agent should interpret and cite output.

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?

Two tight sentences with no filler; the return contents are front-loaded and the interpretive caveat follows. Nothing is wasted, though the second sentence mixes usage guidance with output caveats.

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 convey what comes back (reviews, ratings, brief), but omits volume/pagination, error behavior for a missing or unpublished offering, and how offering_id is sourced. Adequate but with clear gaps for a retrieval tool.

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% and the description never explains the single required offering_id — its format, or that it is obtained from find_offerings. With one undocumented parameter, the description fails to compensate for the schema gap.

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 description uses a specific verb ('Read') and resource ('one product/service') and enumerates the returned payload (reviews, evidence-separated ratings, experience brief). It is clear what the tool does, though it does not explicitly distinguish itself from siblings like get_reputation or find_offerings.

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?

There is no explicit when-to-use guidance or mention of alternatives such as find_offerings for discovery versus get_offering for retrieval by id. The citation directive hints at usage but does not route the agent between sibling tools.

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