get_clip_notes

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

No annotations exist, so the description carries the burden of behavioral disclosure. It adds useful context by specifying the return format (JSON list of notes) and the fields (pitch, start_time, duration, velocity, mute, note_id when available). It does not cover error handling, prerequisites, or empty-list behavior, but the read-only nature is clear from the verb.

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, with the action clearly stated first and return details second. Every sentence provides necessary information, and there is no redundant or unnecessary text.

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?

The tool has a simple purpose and an output schema, and the description covers the return value. However, the complete lack of parameter semantics and any caveats (e.g., MIDI-only, behavior for empty clips) leaves meaningful gaps. An agent would need to guess at how to specify the clip and what conditions might affect the result.

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 input schema shows two parameters (track_index, clip_index) with zero descriptions. The description does not mention these parameters at all, so it adds no meaning about indexing conventions, ranges, or how to identify the target clip. The agent must infer from names alone.

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 a specific verb 'Read' with a clear resource 'all MIDI notes from a clip.' This distinguishes it from sibling tools like add_notes_to_clip and remove_notes_from_clip, which perform different actions. The purpose is unambiguous and focused.

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 implies its use case—when you need to read notes from a clip—but does not explicitly state when to use it versus alternatives, nor does it provide exclusions (e.g., only for MIDI clips). There is no mention of alternative tools or when not to use this tool.

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