get_warp_state

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

With no annotations, the description carries the burden well: it declares 'Side effects: none', explains routing through the Extension Host WebSocket bridge, and states the prerequisite that the AbletonMCPServer Extension must be installed. It omits return-shape and error behavior, but the output schema covers returns.

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 purpose is front-loaded in the first sentence, followed by clean labeled sections for side effects, example, and edge cases. Every line earns its place with minimal waste.

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 two-parameter read tool with an output schema, the description covers purpose, safety, invocation, and prerequisite. The only real gap is index-base/validity guidance, which is minor given the example and output schema.

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 coverage is 0% so the description must compensate. The example 'get_warp_state(1, 0) reads warp data from track 1, clip 0' maps both required positional parameters to meaning, which adds real value, but it never states index base or valid ranges.

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?

States a specific verb ('Retrieve') and resource ('audio clip') and enumerates exactly what is returned: warping status, warp mode, and warp markers. The read-only scope clearly complements the sibling set_warp_state without needing to name it.

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 example shows invocation and the sibling set_warp_state implies this is the read counterpart, but there is no explicit statement of when to use this rather than alternatives or what preconditions select it. Usage is implied rather than stated.

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