read_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 any behavioral traits such as whether the operation is read-only, what it returns (despite an output schema existing), potential side effects, or error conditions. The description is too sparse to inform an agent about the tool's behavior.

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 extremely short, but it is under-specified rather than concise. It lacks essential details and is not front-loaded with actionable information. Every sentence should earn its place; this single sentence provides almost no value.

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?

Given there are two parameters (one required) and an output schema, the description is grossly incomplete. It does not explain how to select the MIDI clip (via slot/track), what the output contains, or any assumptions. An agent cannot reliably call this tool based on the description.

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%, so the description must compensate. It does not explain 'slot' or 'track' at all, nor their roles or how they affect the result. The description adds no meaning beyond the raw schema names.

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 'The notes of a MIDI clip' is a noun phrase without a verb, so it doesn't clearly state the action. It adds the context of MIDI clip but does not say what the tool does (e.g., 'read', 'retrieve', 'get'). It is nearly a restatement of the tool name 'read_notes' and does not differentiate from any siblings.

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?

There is no guidance on when to use this tool versus alternatives, no mention of context, prerequisites, or when not to use it. The description provides no decision support for an agent.

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