get_midi_item

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

Annotations already declare readOnlyHint=trueainer, and the description aligns by presenting a read-only get operation. The description adds useful return-shape context (position, length, note count), but it does not disclose indexing assumptions, failure behavior, or edge cases for the two required integer parameters.

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 short and front-loaded, with the core intent in the first sentence and a useful but compact return summary in the second. There is no filler or repetition of schema fields.

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?

For a simple two-parameter getter this is partly sufficient, but the missing parameter semantics and lack of usage routing leave real gaps. With no output schema, the description's partial return summary is helpful, but alone it does not fully equip an agent to call the tool 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% and the description does not compensate. It never explains what track_index and item_index mean, whether they are zero-based, or how they relate to the returned object. The agent must guess the parameter semantics from the bare parameter 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 clearly states a specific verb and resource: 'Get information about a MIDI item.' This distinguishes it from mutation tools like add_midi_note or delete_midi_note. However, it does not differentiate from the nearby generic get_item_info sibling, so it stops short of full sibling-level clarity.

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 about when to use this tool versus alternatives such as get_item_info or get_midi_notes. The description says what it does, but not when an agent should prefer it over sibling tools, nor any exclusions.

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