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 fully covered without the description. The description's additions are thin: "paginated" restates the cursor parameter that the schema already exposes, and it says nothing about result volume, cursor lifetime, or rate limits.

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 short sentences: the capability and sorting are front-loaded, and the cross-references follow. Every clause earns its place with no filler.

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 list tool with full annotation coverage but no output schema, the description covers purpose, sorting and sibling routing adequately. The remaining gap is the undocumented half of the parameters and any hint of the review object's shape, but the tool name and annotations make it callable.

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 only 43%, so the description must carry weight, yet it only partially covers the sort enum ("helpfulness, recency, or score" maps loosely onto most_helpful/newest/highest/lowest). The phase, limit, cursor, context and response_format parameters get no explanatory text at all.

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 paginated community reviews for a fragrance") plus the sortable dimensions, and explicitly routes to two named siblings (fragrance_get, fragrance_get_wearing_stats). An agent can distinguish this from fragrance_get without opening the 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?

The "See also" line gives clear context for what this tool is not for (full profile, aggregate wearing data), which is stronger than most siblings. However, it never mentions fragrance_review_digest or user_get_reviews, which are the closest alternatives, and offers no explicit when-not condition.

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