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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the return shape ('ranked fragrances with scores and movement'), which is useful, but doesn't disclose ranking methodology, chart refresh cadence, or slug-not-found behavior.

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 front-loaded sentences plus a compact See also line. No filler or restatement of the name, though the slug examples duplicate what the schema already lists.

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?

Given the tool is a simple read with annotations covering safety and no output schema, the description covers purpose, examples, return shape, and sibling routing. Minor gaps remain around error/empty-chart behavior, but nothing an agent needs to invoke it correctly is missing.

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 67% and the slug enum examples are repeated between schema and description. The mandatory 'context' analytics parameter is fully documented in the schema, so description adds little; the response_format enum is unmentioned in the description. Baseline 3 is appropriate.

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+resource ('Get a specific chart leaderboard by slug') and gives concrete examples of slugs. It doesn't explicitly contrast with siblings like 'trending' in the description body, but the See also lines route to charts_list and fragrance_get.

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 names alternatives (charts_list to discover slugs, fragrance_get for profiles), which gives clear context for when each applies. It stops short of explicit when-not-to-use conditions, so it's strong but not exhaustive.

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