tasks_cancel

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It adds only one behavioral detail ('releases calendar hold') beyond the name. It omits whether the cancellation is reversible, what permissions are required, what effects occur on related data, or any side effects. For a mutation tool, this is insufficient transparency.

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 brief single sentence, front-loaded with the core action. However, it is too short given the missing parameter and behavioral details, sacrificing completeness for conciseness. It earns a middling score because while it avoids bloat, it under-delivers on content that needed to be present.

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?

Despite the existence of an output schema, the tool has moderate complexity with two parameters, no schema descriptions, and no annotations. The description fails to explain the return value, prerequisites, the meaning of group_id, or the cancellation's broader impact (e.g., whether it deletes the task or just removes calendar hold). It is not complete enough for an agent to use confidently.

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%, meaning the input schema provides no parameter descriptions. The tool description does not mention either parameter (task_id or group_id), leaving the agent to infer their meaning from names alone. It fails to add semantic value beyond what the raw parameter names suggest, which is minimal.

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 'Cancel task' as the action on the resource, with the parenthetical 'releases calendar hold' providing specific context. This distinguishes it from sibling tools like tasks_complete (which likely marks tasks done without cancellation). The verb+resource is specific and unambiguous.

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?

The description offers no guidance on when to use cancel versus alternatives like tasks_complete, tasks_update, or tasks_delete. It does not mention prerequisites, conditions, or when not to use this tool. The parenthetical hint about calendar holds is the only contextual clue, but it is not explicit usage guidance.

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