cancel_job

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent knows this mutates state but is not classified as destructive. The description adds only that the target is a 'matching job,' without saying whether partial progress is preserved, whether cancellation is reversible, or what happens when no job is running.

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?

A single front-loaded sentence with no filler. It is efficient, though arguably too terse to carry the needed behavioral detail.

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 state-mutating job-control tool with no output schema and no supporting annotations beyond the safety profile, the description omits error/edge-case behavior and job lifecycle context. An agent lacks enough to know what happens on cancellation or in the no-job-running case.

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 description coverage is 0%, but there is only one parameter named playlist_id, whose meaning is largely obvious from the name. The description does not clarify the identifier's format or relationship to the job, so it adds minimal value while the near-trivial parameter keeps this at baseline.

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?

States a specific verb ('Stop') and resource ('the running matching job of a playlist'), which is clear enough to distinguish from read tools like status or get_music. It does not explicitly differentiate itself from a hypothetical start/resume counterpart, but the resource scope is unambiguous.

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 versus siblings such as status, sync_playlist, or review_candidates. No preconditions are stated (e.g., whether a job must be running, what happens if none is).

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