get_clip_notes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether this is a read-only operation, what happens if the clip is empty or invalid, or what the return structure looks like. While the name implies a getter, the lack of explicit safety or error semantics is a notable gap.

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 exceptionally concise, with a single clear purpose statement followed by a compact parameter list that adds value without redundancy. Every sentence earns its place, and the information is front-loaded for quick parsing.

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 tool with no output schema and no annotations, the description is incomplete. It explains what the tool does and the parameters, but fails to describe the return format (e.g., an array of notes with pitch, velocity, duration, and timing properties) or error behavior when the clip doesn't exist. This is a significant gap for an agent that needs to process the results.

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 schema provides only parameter names and types, but the description adds meaningful context: track_index is described as 'the index of the track containing the clip' and clip_index as 'the index of the clip slot containing the clip'. This clarifies the role of each parameter, though it omits details like zero-based indexing or value ranges.

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 action ('Get all MIDI notes') and the resource ('a clip'), leaving no ambiguity about what the tool does. It also distinguishes itself from sibling tools like add_notes_to_clip and remove_notes, as the scope is retrieval of all existing 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?

The description provides no guidance on when to use this tool versus alternatives such as get_clip_loop or quantize_clip_notes. It simply states what it does without any context about prerequisites, related operations, or scenarios where another tool would be more appropriate.

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