ableton_get_clip_notes

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

With no annotations, the description must fully disclose behavior. While it implies a read-only operation via 'Read', it omits important details such as whether the clip must exist, what happens if no notes are present, or the structure of the returned data.

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 a single, front-loaded sentence with no extraneous words. However, it could benefit from additional context about the output or preconditions without sacrificing conciseness.

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 the lack of output schema and 0% parameter descriptions, the tool description provides insufficient information for an agent to use it correctly. It does not specify return format, error conditions, or the required state of the clip.

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 0% description coverage for its two parameters ('trackIndex', 'clipSlotIndex'). The description does not explain their meaning, valid ranges, or relationship to Ableton Live's structure, forcing the agent to rely solely on 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 explicitly states the action ('Read') and the resource ('MIDI notes from an existing Ableton Live clip'), clearly distinguishing it from sibling tools like 'ableton_create_midi_clip' or 'ableton_delete_clip'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'ableton_get_device_parameters' or 'ableton_analyze_audio'). The description only states the basic operation without context or exclusion cases.

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