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

The annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower. The description adds useful behavioral context: catalogue size, no-argument list-all behavior, query matching across vendor/name/slug, and returned fields including firmware version when stated.

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?

The description is compact and front-loaded, starting with the primary action and scope before covering no-argument behavior, filtering, return fields, and the recommended next tool. Every sentence contributes useful information.

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?

With annotations and an output schema already present, the description provides enough context to call the tool correctly, including default listing behavior, query semantics, and return fields. Minor gaps remain around how `kind` and `vendor` interact with `query` and what the default limit is.

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 high at 80%, so the schema already documents most parameters. The description adds a useful `query` example and explains slug usage, but it does not clarify the `kind`, `vendor`, or `user_id` filters beyond what the schema provides.

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?

The description states a specific verb and resource: find/list device drivers in the catalogue, with concrete scope (about 980 synths, drum machines, controllers and DAWs). It also distinguishes this tool from list_routes by explaining that a returned slug should be passed to list_routes for the full CC/NRPN/SysEx map.

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 clearly explains the default behavior with no arguments and how `query` narrows results, plus it names the follow-up alternative `list_routes`. It does not explicitly cover when to prefer `vendor` or `kind` filtering over `query`, or state exclusions, so it falls short of a full when/when-not guide.

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