get_clip_notes

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

No annotations provided; description does not disclose that the tool is read-only, non-destructive, or any side effects. For a read operation, stating that it does not modify state would be helpful.

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?

Two short sentences and a parameter list are concise but lack structure. No examples, return format, or usage context. The parameter list is redundant with the input schema.

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, no description of the return value format (e.g., note properties like pitch, velocity, start time). For a tool that retrieves notes, this omission significantly reduces completeness.

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 0%. The description repeats parameter names but adds no meaning beyond the schema (e.g., what constitutes a valid track_index or clip_index, or how they relate to Ableton Live's structure).

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 clearly states the tool retrieves 'all MIDI notes from a clip' with specific verb and resource. However, it does not differentiate from similar getter tools like get_clip_automation or get_clip_loop, relying solely on the mention of 'notes'.

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 alternatives (e.g., get_clip_automation, remove_notes). No prerequisites or context about clip types (MIDI vs audio).

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