get_clip_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 does not disclose what the output format is (e.g., list of note objects with properties), whether the tool is read-only, or any constraints (e.g., only works with MIDI clips). This is insufficient for behavioral 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 very concise: one sentence for purpose and a parameter list. It avoids unnecessary words, though it is so minimal that it lacks context. Still, conciseness is a positive trait.

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?

While an output schema exists (unseen), the description does not mention the return type or structure. For a tool that retrieves MIDI notes, the agent lacks information about what 'notes' entails (e.g., pitch, velocity, timing). The description feels incomplete for the task complexity.

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 description explicitly documents both parameters as 0-based indices, adding meaning beyond the schema which only provides titles. With 0% schema description coverage, this compensation is valuable, though it could be more detailed (e.g., range of valid indices).

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 'Get all MIDI notes in a clip.' It uses a specific verb and resource, distinguishing it from sibling tools like get_clip_info (clip metadata) and set/add/remove_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 no guidance on when to use this tool versus alternatives. It lacks context about prerequisites (e.g., clip must be a MIDI clip) or when to choose get_clip_notes over other note-related tools.

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