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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the data is public and cached per fragrance, which tells the agent results are stable and cheap to re-request.

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 sentences plus a one-line routing hint, with the core purpose front-loaded before the disambiguation. Every clause carries information; nothing is restated from the name or annotations.

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?

For a read-only digest tool with no output schema, the description adequately conveys what comes back (themes, consensus, standout opinions) and the public/cached nature. Only the unexplained response_format enum keeps it from being fully complete.

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 moderate (67%) and the description adds no parameter-level detail at all. The heavily-documented 'context' parameter is fully explained by the schema, but response_format has an enum with no description in either place, so the description misses a chance to compensate.

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 and resource ('Get a concise AI-generated digest summarizing a fragrance's community reviews') and enumerates the content shape (key themes, consensus, standout opinions). The 'See also' line contrasts it with fragrance_get_reviews and fragrance_get, so an agent can pick it without opening other 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?

The sibling routing line makes the choice clear: digest for summarized consensus, fragrance_get_reviews for individual reviews, fragrance_get for the full profile. It stops short of an explicit 'use this when you want X rather than Y' rule, but the alternatives and their scopes are supplied.

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