Create hand Ableton mapper

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

Annotations already flag readOnlyHint=false and openWorldHint=true; the description adds concrete behavioral details: it outputs four mapped signals, creates a skeleton overlay, and can relink an existing TDA_Mapper to the generated CHOP. It does not describe failure modes or what happens if the target container already exists, but the destructiveHint=false plus the explicitly non-destructive relinking language align with the annotations. No contradiction, and the extra detail earns a 4.

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 two sentences, front-loaded with the core purpose, and each clause adds value: outputs, overlay, relinking, dependency. No filler or redundant restatement of the title. This is exemplary conciseness.

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?

Given a complex build action with 20 parameters and no output schema, the description provides a strong high-level summary of what is created and how it connects to existing components. It stops short of documenting return values or detailing the network structure beyond the named outputs, but the schema covers parameters and the annotations cover safety. The balance is reasonable, though a bit more on expected output (e.g., created container path) would push it to 5.

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?

All 20 parameters are documented in the schema (100% coverage), so per rubric the baseline is 3. The description itself does not add parameter-specific guidance beyond the schema; it mentions the output maps (pinch/wrist) which relate to invert flags, but that's contextual rather than parameter-level detail. The schema descriptions are self-sufficient, so a 3 is appropriate.

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 opens with a specific verb ('Build') and names the exact resource (MediaPipe-hands → TDAbleton TDA_Mapper performance control network). It enumerates concrete outputs (map1–map4, skeleton overlay) and explicitly distinguishes the dependency story ('Uses TDAbleton directly; AbletonMCP is not required'). This separates it clearly from sibling hand-tracking and gesture-bus tools.

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 specifies the use case—building a hand-driven Ableton mapper—but does not explicitly name alternative tools or state when not to use it. The dependency note ('AbletonMCP is not required') gives a hint, and the mention of optionally relinking an existing TDA_Mapper implies it can augment an existing setup. However, it lacks an explicit 'use this instead of X' statement, so it gets a 4.

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