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

Annotations already declare readOnly/idempotent/non-destructive, and the description confirms read-only. Beyond that it discloses the payload of each recipe — inputs, ordered tool calls, outputs, credit/time estimate, and how to VERIFY success from the response — which is genuine behavioral context an agent needs before trusting the guide.

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?

Front-loaded with a clear scope statement, but the recipe enumeration is a single very long em-dash sentence that becomes a wall of text. Every clause is informative, yet the structure could be tightened.

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, so the description carries the burden of explaining return content — and it does, listing inputs, ordered tool calls, outputs, estimates, and verification guidance. Complete for a one-parameter read-only reference tool.

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 100% and already documents omitting name to list all. The description adds value by naming the index concept and tying recipes to a use_when selector, plus mentioning aliases implicitly in the recipe list — marginal but real beyond the schema.

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?

Names a specific resource — a catalog of named multi-step pipelines — and enumerates them (stems, session, cover, transcribe, render-midi, timbre-transfer, analyze-song, etc.), so the agent immediately knows this is a reference/guide tool rather than an action tool. It is cleanly distinguished from the many sibling action tools that actually perform those steps.

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?

Explicitly states the two invocation modes: no name returns the index (to pick by use_when), a name returns the full recipe. What is missing is guidance on when to consult this versus calling sibling tools directly, though the recipe content description implies it should be read before assembling a multi-step workflow.

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