start_playback

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

With no annotations, the description should disclose behavior like what happens if already playing or if transport is in a specific state. Only states 'start playing,' leaving agent uninformed about constraints or side effects.

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?

Single sentence is concise and front-loaded. Could add behavioral or usage notes without becoming verbose, but current structure is clean.

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?

No output schema and no annotations; description lacks information on return behavior, error conditions, or relationship to sibling tools like 'continue_playback.' Incomplete for guiding proper invocation in a complex toolset.

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 sole parameter is an injected context object (Context), not a user-facing input. The description adds no parameter info, but this is acceptable because the parameter is standard and does not require elaboration beyond the schema definition.

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?

Description states 'Start playing the Ableton session,' which is a clear verb+resource. It distinguishes from the sibling 'stop_playback' and implies a starting action, but does not explicitly differentiate from 'continue_playback'.

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 on when to use this tool versus alternatives like 'continue_playback' or prerequisites such as whether the session must be stopped. Missing context for appropriate usage.

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