ddr_stop

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

No annotations are provided, so the description carries the full behavioral burden. The 'stop/pause' ambiguity is unresolved - does it halt and reset, or merely pause resumable playback? No mention of idempotency, state side-effects, or error behavior when the DDR is already stopped.

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?

A single short sentence with no wasted words, front-loaded with the action. Efficient, though the 'stop/pause' slash construction trades precision for brevity.

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?

Adequate for a trivial one-param, no-annotation tool with full schema coverage, but the unresolved stop-vs-pause ambiguity is a real gap given there is no output schema or annotation to clarify the resulting 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?

Schema description coverage is 100% and the single parameter has an enum documented in the schema. Baseline 3 applies since the description adds no parameter meaning beyond what the schema already provides.

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 (stop/pause) and resource (DDR media player), clearly distinct from siblings like ddr_play or get_ddr_status. The dual 'stop/pause' phrasing is slightly ambiguous about whether these are the same or different behaviors, but the resource and action are clear.

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?

Usage is implied by the verb and sibling context (ddr_play suggests this is its counterpart), but there is no explicit when-to-use, when-not-to-use, or prerequisites guidance. An agent can infer intent but isn't told about conditions like whether the DDR must be playing first.

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