create_scrobble_stop

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

Annotations already cover idempotent and non-destructive hints, and the description adds that this operation stops or finishes watching. However, it does not disclose auth requirements, response behavior, or what happens to an active scrobble state.

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 with the action and endpoint, followed by a useful payload-discovery instruction. There is no filler or redundant elaboration.

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?

The /schema pointer and annotations provide a reasonable basis for invoking the tool, especially with an open-world body parameter and an output schema present. Still, it lacks usage differentiation among scrobble tools and any mention of prerequisites or side effects, so it is not fully self-sufficient.

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 exposes an opaque 'body' object with additionalProperties=true, so the description must compensate. It correctly identifies body as the request payload and instructs the agent to consult the matching GET or /schema endpoint, but it does not list or exemplify expected fields.

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 states a specific action, 'Stop or finish watching in a media center', and provides the endpoint POST /scrobble/stop. It semantically distinguishes itself from siblings like create_scrobble_start and create_scrobble_pause, though it does not explicitly reference 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 on when to use this tool versus alternatives such as create_scrobble_pause or create_scrobble_start. The only directive is to read the matching GET or /schema endpoint first, which addresses payload discovery rather than tool selection.

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