cancel_jobs

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

No annotations provided; description does not disclose behavioral traits such as immediate vs. async cancellation, reversibility, permissions required, or impact on running jobs. The verb 'Cancel' implies destruction but lacks detail.

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?

Single concise sentence, but too brief to convey necessary detail. Appropriate length for a simple purpose, but under-informative given parameter complexity.

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?

Despite having an output schema, the description lacks explanation of behavior (e.g., return value, confirmation, side effects). With 10 undocumented parameters and no annotations, the tool is underspecified.

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 description does not explain any of the 10 parameters (e.g., arch, test, build). Schema has zero description coverage, leaving the agent without meaning for each filter field.

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 'Cancel all jobs matching the given filters' clearly states the action (cancel) and resource (all jobs) with a scope (matching filters). It distinguishes from sibling 'cancel_job' implicitly via plural vs singular, but lacks explicit differentiation.

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 tool versus alternatives like cancel_job (single job) or restart_jobs. No context about conditions for execution or exclusions.

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