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 by structured data. The description adds return-payload scope, which is mildly useful, but says nothing about auth, rate limits, or lookup failure behavior when neither id nor slug matches.

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: the capability and return payload are front-loaded, then a compact sibling-routing line. No filler, and the highest-value information comes first.

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 lookup with full annotation coverage and no output schema, the description supplies the return-field inventory and sibling alternatives, which is nearly everything an agent needs. The only gap is disambiguation between passing id versus slug and the response_format behavior.

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 75%, and the schema already documents id, slug (with the same 'tom-ford/oud-wood' example), and the lengthy context parameter. The description's inline slug example duplicates the schema rather than adding format rules, and response_format is never mentioned, so it stays at the baseline 3.

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 the full profile for a single fragrance') plus the two accepted identifiers (UUID or slug) and an inline slug example. It also enumerates the payload (notes pyramid, accords, FOTW classification, perfumer, community score), so an agent knows exactly what it will get and how it differs from search or similar tools.

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' block routes to three siblings with the condition that selects each: fragrance_similar for similar accord profiles, fragrance_get_reviews for reviews, and fragrance_get_wearing_stats for wearing stats. That is strong positive routing, but there is no explicit when-not-to-use or statement of prerequisites, so it stops short of a 5.

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