transport_stop

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

Annotations already indicate the tool is mutating (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds the planning/execution duality ('plan or stop'), which is useful, but does not elaborate on side effects, reversibility, or state changes beyond what the schema implies.

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?

A single, compact sentence conveys the core action without redundancy. It is front-loaded and efficient, earning every word. No fluff or unnecessary detail.

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 transport control operation, the description is largely sufficient given the schema and annotations. However, in the context of many sibling tools (e.g., stop_all_clips, panic, transport_play), it could briefly mention that it targets the global transport, not individual clips. Still, it is adequate for the agent to proceed.

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 100%, with each parameter already documented (dryRun, planHash, confirmationToken, expectedStateVersion). The description adds no additional semantic meaning beyond what the schema provides, so a baseline 3 is appropriate.

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 states a specific action ('stop') and a clear resource ('Ableton transport playback'). It clearly distinguishes from the sibling 'transport_play' and is unambiguous about its scope. The verb 'plan or stop' also signals the two-phase workflow.

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 description implies usage (when you want to stop transport) but does not explicitly mention alternatives like 'stop_all_clips' or 'panic', nor does it state when not to use it. It is functional but leaves disambiguation to the agent's reasoning.

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