get_clip_notes

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

Annotations already set readOnlyHint and idempotentHint. The description adds that the tool fails for empty slots or audio clips, and mentions that newer Live versions may add expression fields. This provides useful behavioral context beyond annotations, though it could clarify behavior for empty vs non-existent clips.

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 plus a brief list of note fields, all front-loaded and to the point. No wasted words.

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 that an output schema exists (not shown), the description provides sufficient context: what fields are returned, failure conditions, and sibling distinction. It is complete for a tool with good annotations and output schema.

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 100% with each parameter having a description. The description does not add additional meaning beyond the schema; baseline 3 is appropriate as it doesn't compensate further.

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 explicitly states returning every MIDI note from an existing Session-view MIDI clip, providing a specific verb (return), resource (MIDI notes), and context. It distinguishes from siblings like get_clip_info by mentioning it is for notes and not clip properties.

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 clearly states when to use (existing session-view MIDI clip) and when not to (empty slot, audio clip). It explicitly recommends get_clip_info for clip properties, providing an alternative.

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