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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context on top: 'free, no key needed', that no args returns the whole catalog, and exactly what each entry contains (render call, timbre preset, range, chord capability, presets, demo). That is genuine behavioral disclosure beyond the structured fields.

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 the core purpose and the filtering modes in one dense paragraph where every clause carries information. It is long and parenthetical-heavy, but there is no filler sentence to remove without losing catalog semantics.

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?

There is no output schema, so the description carries the burden of describing return contents — and it does, enumerating call, range, chord support, presets, and demo per entry. An agent has everything needed to call it and interpret the response.

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?

Despite 100% schema coverage, the description adds meaning the schema doesn't: illustrative queries ('warm low brass'), that query results are ranked best-first, that pitches filters to instruments whose range holds every pitch, and that id returns one instrument in full with all presets. This meaningfully upgrades parameter interpretation.

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 — the full instrument catalog — and defines scope precisely: every instrument doseedo can render notes on, broken down by families and with concrete exotic examples. An agent can immediately distinguish it from siblings like doseedo_list_plugins or doseedo_train_instrument.

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 tells the agent to 'read it before writing a part' and ties it to the downstream tool doseedo_render_midi, which is strong when-to-use guidance. There is no explicit when-not or named alternative, but for a catalog tool the routing is essentially unambiguous.

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