stop

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

With no annotations provided, the description carries full burden but only states the action ('Stop playback'). It doesn't disclose behavioral traits such as whether this requires specific permissions, what happens to paused vs. playing media, if it's reversible, or any side effects. The description is minimal and lacks necessary context for a mutation tool.

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 extremely concise ('Stop playback.') with zero wasted words, making it front-loaded and easy to parse. Every word earns its place by directly conveying the core function.

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 tool's simplicity (0 parameters, no annotations, but has an output schema), the description is minimally complete. However, as a mutation tool with no annotations, it should ideally include more behavioral context (e.g., effects, prerequisites). The output schema reduces the need to explain return values, but the description remains sparse for a tool that likely alters system state.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't add parameter details, but with no parameters, this is acceptable. Baseline is 4 for zero parameters as no additional explanation is needed.

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 'Stop playback' clearly states the tool's function with a specific verb ('Stop') and resource ('playback'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'play' or 'record' beyond the obvious semantic difference.

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. While the name implies it stops ongoing playback, there's no mention of prerequisites (e.g., requires active playback), exclusions, or relationships to sibling tools like 'play' or 'record'.

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