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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true); the description adds genuine context beyond them by disclosing result ordering (Joker and Millésime distinctions surfaced first) and that each entry includes a link to its review.

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?

A single dense sentence with no filler; the resource (recordings reviewed by Crescendo) is front-loaded, followed by ordering and content details. Slightly packed, but every clause earns its place.

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?

No output schema exists, and the description usefully sketches what comes back (ranked reviews with links). For a two-parameter read-only tool this is nearly sufficient; only the undocumented 'limite' parameter 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 50%: 'compositeur' is documented ('Nom ou identifiant Pauline') but 'limite' has no description anywhere. The description references the composer concept but says nothing about the limit parameter, so it does not compensate for the coverage 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?

States a specific verb+resource: recordings of a composer reviewed by Crescendo Magazine, including Joker/Millésime distinctions and review links. An agent can tell it returns disc reviews, but the description never contrasts it with siblings like fiche_compositeur, leaving the differentiation to be inferred.

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?

It implies a composer must be supplied ('Enregistrements de ce compositeur'), but gives no explicit when-to-use, when-not-to-use, or alternative tool. With three siblings, the absence of routing guidance is a real gap.

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