get_notes

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

No annotations are provided, so the description carries the full burden. It states the return data (pitch, start time, duration, velocity) but does not explicitly confirm it is a read-only operation, mention prerequisites (e.g., MIDI clip required), or describe error conditions. The description is adequate but minimal for a simple getter.

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 concise sentences that front-load the purpose and key return values. Every sentence adds value with no extraneous information.

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 output schema exists, so the description's mention of return fields is helpful but not essential. However, the lack of parameter explanation and missing behavioral context (e.g., handling of non-MIDI clips) leaves the description moderately incomplete for an agent to use correctly.

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%, yet the description fails to explain what track_index and slot_index refer to. These parameters are essential for identifying the target clip, and the description provides no additional meaning beyond the bare schema names and types.

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 tool retrieves all MIDI notes from a MIDI clip, which is a specific verb+resource combination. It distinguishes itself from siblings like add_notes (which adds), clear_notes (clears), and get_clip (which retrieves broader clip data).

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 when an agent needs to extract MIDI note data from a clip. However, it provides no explicit guidance on when not to use it (e.g., for audio clips) or alternatives such as get_clip for general clip info.

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