play

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

It mentions the key behavioral constraint that it only works from paused state, not stopped, which is important given no annotations. But it does not disclose what happens if the condition is violated or any other side effects.

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 two short sentences with no redundant information. It is tightly written and directly states the essential constraint.

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?

For a simple play control, it provides the essential condition but lacks parameter details and error behavior. The output schema presumably covers return values, but the description alone is not fully complete for an agent to invoke it correctly.

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?

The schema has 0% description coverage, and the description does not explain the 'player' parameter beyond saying 'on a player'. It fails to specify whether it's an ID, name, or how to obtain it, leaving the parameter ambiguous.

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 clearly states the action (resume playback) and the target (a player), and it specifies the precondition from paused state. This differentiates it from 'play_item' which likely plays a specific item rather than resuming.

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?

It provides a clear precondition ('Only works from paused') which guides when to use it. However, it does not explicitly compare against alternatives like play_item or pause, so the decision boundary is not fully explicit.

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