cancel_job

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

Mentions graceful termination, adding context beyond schema. However, no annotations are provided, so description carries full burden. Lacks details on reversibility, dependencies, or audit trail implications beyond the reason parameter.

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 sentence, front-loaded, no unnecessary words. Efficient and clear.

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?

Adequate for a simple mutation tool with 3 parameters and no output schema. Lacks details on prerequisites and post-conditions, but sibling context provides some differentiation.

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 coverage is 100%, so description adds minimal value beyond parameter names and defaults. The mention of 'graceful' relates to force parameter but schema already covers that. Baseline score applies.

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?

Clearly states verb 'Cancel', resource 'iSuite job', and action 'terminated gracefully'. Distinguishes from siblings like cancel_batch and retry_job.

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?

Describes when to use (for a currently running job) but lacks guidance on when not to use, such as for completed jobs, or how it compares to cancel_batch. No explicit alternatives or exclusions.

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