get_clip_notes

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

With no annotations, the description must carry the transparency burden. 'Read' clearly implies a non-mutating operation, and 'Session clip' narrows the context. However, it does not disclose edge-case behavior, such as what happens for audio clips, empty MIDI clips, or invalid track/clip indices.

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 compact and front-loaded: one clear purpose sentence followed by a concise parameter list. Every sentence earns its place, and the bullet format improves scannability without excessive verbosity.

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 simple two-parameter read tool, the description covers the core purpose and parameter semantics. Since an output schema exists, return-value details are not required here. The main gap is the lack of guidance about audio clips vs. MIDI clips or error behavior, but the tool is still adequately specified for most straightforward calls.

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 only provides parameter names and types, so the description adds genuine value by explaining that track_index is a 1-based track number and clip_index is a 1-based clip slot number. This is useful and goes beyond the schema, though it stops short of describing ranges or invalid-input behavior.

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 and resource: 'Read the MIDI notes of a Session clip.' This clearly distinguishes it from related siblings like get_clip_properties or add_notes_to_clip by focusing on reading note data. The 1-based parameter clarifications further support the tool's purpose.

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 usage: call it when you need the MIDI note data of a Session clip. However, it provides no explicit guidance about when not to use it or which sibling tools might be better alternatives for different tasks, such as get_clip_properties or arrangement-oriented clip tools.

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