Cancel Session Job

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

Annotations indicate mutation (readOnlyHint false) and idempotency (idempotentHint true). The description adds value by mentioning the AbortSignal mechanism. However, it does not disclose what happens after cancellation (e.g., job state, return behavior) or any side effects.

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?

Two sentences that front-load the core purpose and add one relevant detail. Conciseness is good, but the omission of parameter information makes it incomplete.

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?

Given the lack of output schema and parameter descriptions, the description is insufficient. It does not explain return values, error handling, or behavior for non-existent jobs, making it hard for an agent to rely on this 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?

No parameter descriptions are provided. With schema coverage at 0% and 5 parameters, the description must compensate but does not mention any parameter, leaving the agent without guidance on how to specify session_id, job_id, reason, etc.

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 the action (request cancellation) and resource (running background jobs in a durable session). The mention of AbortSignal adds technical detail but does not explicitly differentiate from sibling tools; however, the tool's function is distinct enough among the listed siblings.

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. The description does not mention prerequisites, typical scenarios, or situations where this tool should be avoided.

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