Connect MIDI MPE controller

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

Annotations already indicate readOnly=false, openWorldHint=true, and destructiveHint=false, so the 'Create' action is consistent. The description adds that it builds an expressive scaffold with zone/expression maps, but does not disclose side effects like whether it modifies the project, requires a physical device, or creates outputs beyond a scaffold.

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 a single sentence that is reasonably concise and immediately states the core action. It is front-loaded with 'Create an expressive MIDI MPE input/output scaffold', though the term 'expressive' is somewhat subjective and adds little semantic value.

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 7 parameters, no output schema, and no usage guidance, the description is insufficient for an agent to fully understand tool behavior. It does not explain what happens after creation, how the scaffold is exposed, or what the parameters mean, leaving significant gaps.

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 only 29%, and the description compensates poorly. It does not explain any parameter by name; 'device_name', 'include_output', 'expression_count', and 'lower_zone_channels' remain unclear beyond their names, and the description only vaguely hints at zones and expression maps.

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 uses a specific verb ('Create') and names the resource ('MIDI MPE input/output scaffold') with concrete elements like zone/expression maps for pressure, timbre, pitch bend, and note channels. This distinguishes it from the many sibling connect/create tools, though the verb 'Create' slightly clashes with the tool name's 'Connect'.

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 description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It does not mention the openWorldHint or any conditions for connecting an MPE controller, leaving the agent to infer usage from the name alone.

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