media_control

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

No annotations provided; description only lists actions but does not disclose side effects (e.g., stopping a source, requiring an active source) or prerequisites. Agent lacks information on what happens when an action is performed.

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?

Description is a single sentence, very concise and front-loaded with purpose. However, it lacks structure to separate parameter details or usage notes.

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 3 parameters, no output schema, and no annotations, the description is insufficient. Missing details on input_name source, dry_run semantics, and overall behavior of the tool.

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 0%; description adds meaning to 'action' by listing values, but 'input_name' and 'dry_run' are unexplained. With 3 parameters, partial coverage leaves significant gaps.

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?

Description clearly states the verb 'control' and resource 'media source', and lists specific actions (play, pause, restart, stop, next, previous), making the purpose unambiguous and distinct from sibling tools like start_stream or set_mute.

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 tool versus alternatives like switch_scene or set_volume. The description does not specify prerequisites or context for the actions.

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