start_playback

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

With no annotations provided, the description carries the full burden of disclosing behavior, but it only says 'Start playing' without noting side effects, prerequisites, or whether it resumes from playback position. This is a straightforward action, but the lack of any behavioral detail is a gap.

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 exceptionally concise: one action sentence plus a parameter explanation, both front-loaded. Every sentence adds value, with no redundant information or verbose phrasing.

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?

Despite its brevity, the description covers the essential purpose and the only parameter, making it adequate for a simple transport control with no output schema. It lacks usage guidelines and behavioral nuances, but the tool's low complexity means the description is close to complete.

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 description explicitly explains the user_prompt parameter as 'the original user prompt that led to this tool call (for telemetry)', adding meaning beyond the schema's title and default. Since schema coverage is 0%, this compensation is valuable, though the parameter is trivial.

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 the action 'Start playing' with the resource 'the Ableton session', making it distinct from siblings like stop_playback (which stops transport) and fire_clip (which launches a specific clip). The verb+resource combination is specific and unambiguous.

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 provides no guidance on when to use this tool versus alternatives, such as when to use fire_clip for individual clips or stop_playback for stopping. It only states what it does, leaving the agent without contextual cues for selecting this over sibling tools.

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