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

Mentions idempotent on terminal states, which is key for a cancel operation. No annotations provided, so description carries burden; could elaborate on side effects or auth requirements but adequate.

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, front-loaded with core action and context. No wasted words.

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?

Covers purpose, usage guidance, and key behavioral trait. Output schema exists so return values not needed. Lacks mention of prerequisites or result handling, but sufficient for the tool's simplicity.

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?

Single parameter job_id is a string, no extra description beyond schema. Schema coverage is 0%, but parameter is simple and self-explanatory; no additional format or source guidance given.

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?

Description clearly states it cancels an in-flight job for multi-step plans (job_*), distinguishing from single-action tasks.

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?

Explicitly tells when to use this tool (for job_* plans) and when not to (use actionlayer_cancel for tkt_* tasks). Also notes idempotency on terminal states.

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