get_clip_notes

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

With no annotations, the description carries the transparency burden. It clearly signals a read-only operation via 'read' and lists the return fields, which is strong behavioral disclosure. It does not mention error cases or index conventions, but for a pure read tool it is sufficient.

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 concise (four sentences) and well-structured, opening with the core purpose, then return values, use cases, and parameters. Every sentence adds value and nothing is redundant.

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 description covers the tool's purpose, return values, use cases, and parameters, which is nearly complete for a read-only tool. It lacks error handling notes and explicit index conventions, but the absence of an output schema is well mitigated by the enumerated return data.

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 has zero description coverage, but the description includes a Parameters section that explains each parameter, including the telemetry role of user_prompt. This fully compensates for the schema's lack of descriptions.

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 out of a clip' with a specific verb and resource. It enumerates the exact data returned (pitch, start_time, duration, velocity, mute state, clip name, length) and distinguishes itself from related tools like add_notes_to_clip and get_arrangement_clip_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 explicit use cases: 'inspecting what's already in a clip before editing it' and 'reading back what add_notes_to_clip wrote.' This gives clear context, but it does not explicitly mention alternatives like get_arrangement_clip_notes, so it falls just short of full exclusion guidance.

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