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

Annotations already indicate destructiveHint=true and readOnlyHint=false, and the description aligns by stating 'Cancel' and 'stop'. It adds behavioral details beyond annotations: it specifies 'pending' tasks only and that terminal history is preserved, which is useful context for the agent.

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 a single sentence that front-loads the primary action and includes the key scoping condition ('pending') and side-effect ('preserving terminal history') without waste. It is concise and well-structured.

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?

The tool is simple with one parameter and an output schema, so the description need not explain return values. However, it omits any guidance on the 'task_ref' parameter and lacks usage guidance, leaving some gaps for an agent deciding how to invoke it correctly.

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?

The schema has 0% description coverage, and the description provides no explanation of the 'task_ref' parameter. The parameter name is somewhat self-explanatory but lacks format, meaning, or examples, so the description fails to compensate for the low coverage.

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?

States a specific action 'Cancel' on a 'pending tenant-owned task' and also mentions stopping 'ordinary Insights recovery', which distinguishes it from other task-related tools like tasks_list or tasks_get_status. However, the phrase 'ordinary Insights recovery' is somewhat domain-specific and could be clearer.

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 mention of when to use this tool versus alternatives. It doesn't say 'use this when you need to cancel a task' or indicate exclusions. The description implies the purpose but gives no explicit guidance on selection.

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