slurm_cancel_job

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

No annotations provided, so description carries full burden. States 'Write operation — recorded in the audit log' and mentions default signal SIGTERM with SIGKILL option. However, does not disclose effects on job dependencies, synchronous nature, or error conditions.

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?

Extremely concise: one sentence for purpose, one for audit note, then bullet-style 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?

Missing output/return value description (likely success/error). No mention of permissions or idempotency. Parameter coverage is good but behavioral gaps remain for a cancellation operation.

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 description's 'Args' section adds meaning: explains job_id, host (overrides env var), signal (default, usage for immediate termination), and gateway_id. Provides context beyond schema definitions.

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?

Clear verb 'Cancel', specific resource 'Slurm job', and identifies as a write operation recorded in audit log. Distinguishes from sibling read tools like slurm_get_job_status and submission tools.

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 explicit guidance on when to use vs alternatives. Mentions it's a write operation but lacks preconditions or cases when cancellation is inappropriate. Implied usage by context, but no exclusion criteria.

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