cancel_job

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

No annotations provided. Description indicates destructive action (cancel), but doesn't disclose immediacy, reversibility, or side effects. Adequate for a simple cancel but could be more explicit.

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?

Very concise: single line purpose followed by structured args. No wasted words, front-loaded with key info.

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?

Output schema exists, so return details are handled. Description covers core action and parameters. Could mention that cancellation is irreversible, but overall adequate for a simple destructive tool.

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 the description adds meaning: job_id as 'SLURM job ID' and transport as 'cluster selector' with values explained. Adds value beyond schema.

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 'Cancel a running or pending SLURM job' – a specific verb and resource. Distinguishes from sibling tools like submit_job, list_jobs, etc.

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?

Provides some context on transport (local vs remote SSH), but no explicit when-to-use or when-not-to-use compared to other tools like cancel_job vs stopping via other means.

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