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

With no annotations, the description carries the full behavioral burden and discloses critical limitations: cancellation only sets a flag, the task exits at the next checkpoint, and hosted endpoints lack a cross-request task handle. It still omits details like idempotency or permission requirements.

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?

The description is short and front-loads the core behavior before the transport caveats. It is dense but every sentence contributes relevant information.

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 one-parameter mutation-like tool with no annotations or output schema, the description covers the key operational caveats well, including checkpoint-based exit and hosted endpoint limitations. It could be more complete by describing what stdio returns or how already-finished tasks behave.

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 description coverage is 100%, so the single task_id parameter is already documented by the schema. The description adds no extra meaning about task_id beyond the cancellation context, which is the expected baseline when schema coverage is high.

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 clearly states the action: setting a task cancellation flag. It is distinct enough from siblings like start_long_task and get_task_status, though it does not explicitly name or contrast those alternatives.

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?

It explains transport-specific behavior, especially that hosted endpoints return an honest_note directing callers to stdio. However, it does not explicitly say when to use this tool versus checking status or starting a task, so usage guidance is implied rather than spelled out.

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