cancel_task

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: cancellation is best-effort and an in-progress native import may complete anyway. It omits permissions, whether partial output is retained, and whether cancellation is reversible, so disclosure is partial.

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 short sentences, front-loaded with the action and then the important caveat. No filler, though the telegraphic style leaves obvious questions unanswered.

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?

For a mutation-ish lifecycle tool with no annotations, no output schema, and an undocumented required parameter, the description is thin. It conveys the best-effort nature of cancellation but not the identifier semantics or what an agent should do after calling it beyond "check status".

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?

There is one required parameter, request_id, with 0% schema description coverage, and the description never mentions it or its expected format (task id vs. import id). It therefore does not compensate for the schema gap.

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?

"Request cancellation" names the action but not the resource being cancelled (task vs. import vs. workflow), and the phrasing largely restates the tool name. The second sentence hints the target is an import job, but an agent cannot distinguish this cleanly from siblings like get_task_status or resume_workflow.

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 statement of when to use this versus get_task_status or other lifecycle tools. "check status" implies a follow-up call but does not say under what conditions to cancel or what the preconditions are.

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