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

Annotations already declare destructiveHint=true, openWorldHint=false, readOnlyHint=false, so safety profile is known. The description adds that terminal history is preserved and that only ordinary Insights recovery is stopped, which is useful, but it doesn't state permission requirements, reversibility beyond preservation, or failure modes.

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?

A single tight sentence with no waste; key scope and preservation constraint are front-loaded.

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?

Output schema exists, so return details need not be explained. However, with a mutation tool with destructive hint and 0% schema coverage, the description is adequate but leaves out parameter semantics and permission/edge-case details an agent needs to invoke 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?

Schema description coverage is 0%, so the description must compensate. It references a task and its scope ('pending tenant-owned', 'Insights recovery') but never explains task_ref or connection_context, nor their format/constraints. The parameters remain unelucidated beyond context clues.

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 verb (Cancel) and resource (task), with a qualifier about scope: 'pending tenant-owned task' or 'remaining ordinary Insights recovery'. An agent understands the action, though distinguishing it from siblings like tasks_get_status/tasks_latest is implicit.

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?

Implied usage over cancelling pending tasks with terminal-history preservation, but no explicit when-to-use versus alternatives (e.g., tasks_latest, tasks_list) or when-not. Context is only partially conveyed.

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