set_draw_mode

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

With no annotations provided, the description must disclose behavioral traits. It only states the enable/disable action and parameter meaning, but does not note any side effects, limitations, or prerequisites, such as requiring a selected MIDI clip or session view.

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 main purpose, and every word adds value. No redundancy or unnecessary detail.

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?

For a simple boolean setter, the description is mostly sufficient, and the existence of an output schema mitigates the need to explain return values. However, given no annotations, it could mention the context of use or any effects beyond the immediate toggle.

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?

The description adds semantic meaning to the 'enabled' parameter by stating 'True to enable, False to disable,' which the schema does not provide (0% schema coverage). This is valuable for the single parameter, fully clarifying its meaning.

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 the specific verb 'Enable or disable' with the resource 'Draw Mode' and context 'for editing in Ableton Live,' clearly distinguishing it from other mode-setter siblings. It identifies the exact function without ambiguity.

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 information about when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. It simply states what it does, leaving the agent without guidance on selection.

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