get_midi_chain_report

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

With no annotations, the description carries the full burden and does disclose the key traits: 'Side effects: none' (safe read), the edge-case return value rewrites_input: false for tracks without such a device, and a worked example of what the report surfaces. It omits connection/permission requirements and any timing or rate considerations.

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?

Front-loaded purpose sentence followed by labeled Side effects, Example, and Edge cases lines. Every sentence carries distinct information and nothing is padded.

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?

No output schema exists, so the description does its part by naming the rewrites_input field and explaining the Note Length scenario. Rewriting the response shape and the index convention would make it fully self-sufficient for a one-parameter read tool.

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% for the single required track_index integer, so the description must compensate. The example get_midi_chain_report(58) confirms an integer index is expected, but it never clarifies whether the index is zero-based or what ordering it indexes into, leaving a real gap for a required parameter.

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?

Names a specific verb (report) and a narrowly defined resource: MIDI effects that rewrite clip input. The phrase 'rewrite what a clip says' plus the Note Length example makes the scope concrete enough to separate it from generic siblings like get_device_chains or list_device_params, though it does not name those alternatives directly.

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?

Gives a clear timing cue ('before writing one'), which implies it should be consulted prior to add_notes_to_clip or clip creation so written durations aren't silently overridden. It stops short of naming an explicit alternative tool or a when-not-to-use condition.

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