Run a Roon transport verb (pause/resume/next/previous/stop)

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

No annotations provided, so description carries burden. Describes that it runs a verb on a resolved zone and returns zoneId, action, and playback state. Also explains zoneId resolution. Could mention idempotency or error handling, but overall transparent.

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 dense paragraph with front-loaded purpose, examples, and caveats. Efficient but some redundancy in listing examples, still concise and structured.

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 moderate complexity, no output schema, and full param coverage, description adequately explains what it does, return values, and usage boundaries. Missing error scenarios but not required.

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 100%, baseline 3. Description adds value by explaining zoneId resolution behavior and giving natural language examples for action values, helping map user intent to enum.

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?

Clearly states it runs transport verbs (pause/resume/next/previous/stop) against a zone. Distinguishes from sibling tools like set_volume by explicitly saying 'verbs only' and directing volume adjustments to now_playing+set_volume.

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?

Explicitly says when to use (common transport verbs) and when not (for 'louder'/'softer' without number, use now_playing then set_volume). Provides examples and conditions, though does not directly name all sibling alternatives.

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