playback_stop

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is carried structurally. The description adds genuinely new behavior: the blast radius is limited to adapter-owned playback in its original scene, and the stop is asynchronous in the sense that it must be verified via status polling.

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?

One front-loaded sentence with no filler. The trailing 'poll status until the measured stop is verified' clause is slightly ambiguous about whether the tool polls internally or the agent must poll, but it is short and worth stating.

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 destructive, zero-required-parameter tool with no output schema, the description covers scope but omits what the response looks like and what an empty call does. It is adequate to act on, but the optional-parameter behavior and verification contract remain underspecified.

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 0% for the single parameter, so the description has to carry that meaning — and it does not mention playback_id at all. It never explains whether omitting this optional parameter stops every adapter-owned playback or falls back to a default, which is the key semantic ambiguity for a zero-required-parameter tool.

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 pairs a concrete verb with a concrete resource ('Stop ... native playback') and adds a meaningful scope qualifier ('only adapter-owned', 'in its original scene') that separates it from a generic playback control. It does not name its closest sibling (playback_status) directly, but the operation is still unmistakable.

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 'only adapter-owned native playback' phrasing implicitly tells the agent when this applies and when it does not (non-adapter playback is out of scope). However, no alternative or prerequisite is named explicitly, and the second clause reads as a workflow instruction rather than a routing rule.

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