media_rewind

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It fails to mention side effects (e.g., does it stop playback?), required conditions (e.g., active media session), or any other behavioral implications beyond the basic action. This is inadequate for a command 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 (3 words), which is efficient but lacks any structural front-loading of key details. While not verbose, it may be underspecified for an agent, warranting a middle score.

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 simplicity (0 parameters, no output schema), the description should still clarify the tool's effect and context among siblings. It does not explain whether rewind is a one-time action or continuous, nor its relation to other media controls, leaving the agent with incomplete understanding.

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?

There are no parameters, and the schema coverage is 100% (empty schema). The description does not add parameter information because none is needed. According to the guidelines, when schema coverage is high, baseline is 3, and the description does not add extra value but is not deficient.

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 'Send media rewind' clearly indicates the action is to initiate a rewind command on media playback. It uses a specific verb and resource, and is distinguishable from sibling tools like 'media_fast_forward' by the direction of playback control. However, it could be slightly more precise about whether it starts rewinding or toggles state, but the purpose is 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?

No guidance is provided on when to use this tool versus alternatives like 'media_fast_forward' or 'media_pause'. The description gives no context about prerequisites (e.g., media must be playing) or usage scenarios, leaving the agent without direction for appropriate invocation.

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