ableton_load_master_device

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

With no annotations, description only states it loads onto master track; lacks disclosure of prerequisites, side effects, or return behavior. Basic but not comprehensive.

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?

Single sentence, no fluff. Efficiently communicates the core action and target.

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?

No output schema, minimal behavioral info; does not explain result, error conditions, or prerequisites for a 4-param tool in a complex ecosystem.

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 coverage is 50% (query and rationale described); description adds no extra meaning for any parameter. Missing parameter details in both schema and description.

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?

Description clearly specifies 'load' action onto 'master track', distinguishing it from siblings like 'ableton_load_device' (likely for non-master tracks) and 'ableton_modify_master' (modifying settings).

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?

No guidance on when to use this tool versus alternative loading tools; no when-to-use or when-not-to-use hints provided.

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