create_scrobble_pause

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

Annotations already establish that this is a non-read-only, idempotent, non-destructive mutation. The description adds that it pauses watching and gives the endpoint, but it does not disclose prerequisites such as an active scrobble/session or side effects on playback progress. This is acceptable given the annotations, though not rich.

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 compact and front-loaded: a one-sentence summary, the endpoint, and a single parameter hint. Every line earns its place and there is no filler.

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 one-parameter, open-body tool with an output schema and annotations covering idempotency and safety, the description is mostly complete. It tells the agent where to learn the body shape, but it is incomplete in not situating pause within the broader scrobble lifecycle relative to start and stop.

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 only provides a generic required 'body' object with additionalProperties true. The description labels it as a request payload and instructs the agent to read the matching GET or /schema endpoint to discover expected fields, which is important given the 0% schema description coverage. It does not enumerate fields, but that is reasonable for an open-world body.

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 opening line 'Pause watching in a media center' names a specific action and target resource, and the POST /scrobble/pause endpoint anchors it clearly. It is distinguishable from siblings like create_scrobble_start and create_scrobble_stop, though it does not explicitly contrast with them.

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?

There is no guidance about when to use this tool instead of create_scrobble_start or create_scrobble_stop, nor any indication of the pause/stop distinction. The only conditional instruction is about reading the GET or /schema endpoint for body fields, which is parameter guidance, not usage guidance.

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