get_clip_notes

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

No annotations are present, so the description must convey behavioral traits. It states the output format (list of notes with fields) but does not explicitly confirm it's a read-only operation or mention any side effects. This is adequate but minimal; a statement like 'This is a read-only operation' would improve transparency.

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, directly states the purpose and output fields. Every word contributes value; no 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?

For a simple read tool with an output schema (not shown but confirmed present), the description covers the return fields. However, it omits guidance on parameter semantics and potential edge cases (e.g., what if clip doesn't exist), leaving minor gaps.

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%, meaning the schema provides no parameter descriptions. The tool description does not explain what 'track_index' or 'clip_index' refer to (e.g., 0-based indexing, required to identify the clip). Despite a baseline of 4 for zero params, the failure to compensate with any parameter info significantly reduces value.

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 'Read all MIDI notes from a session clip' with a specific verb and resource. It distinguishes itself from sibling tools like 'add_notes_to_clip' (write operation) and 'get_arrangement_clip_notes' (reads from arrangement clip).

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 is provided on when to use this tool versus alternatives. For example, it does not mention that this tool is for session clips only, unlike 'get_arrangement_clip_notes' for arrangement clips, nor does it indicate prerequisites such as the clip must exist.

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