media_stop

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, and the description adds no behavioral context beyond restating the verb. It doesn't explain playback state after stopping, whether it targets all players or one, or any error conditions.

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 short sentence with zero filler and the action front-loaded. It is efficient, though the brevity comes at the cost of any context that would help selection.

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?

The tool is simple with no required parameters and adequate annotations, so a terse description is defensible. Still, the ambiguity of the optional 'player' argument and the overlap with media_play_pause leave an agent with unanswered questions before invoking.

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 coverage is 100% and the single optional 'player' parameter is documented in the schema, so the baseline 3 applies. The description doesn't clarify what omitting 'player' means, which is the one thing the schema can't say.

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?

States a specific verb and resource ('Stop media playback'), so the action is unambiguous. It does not differentiate from the closely related sibling media_play_pause or stop_recording, so an agent cannot tell from the description alone which is the right stop-like tool.

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 versus media_play_pause (which also halts playback) or whether stop differs from pause/resume semantics. Nothing says what happens with no player specified — stop all players, or only the default one.

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