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

The annotations already disclose that this is a non-read-only, open-world, destructive, non-idempotent operation. The description adds useful scope by saying it affects exactly one task and can both tick and untick it, but it does not explain permissions, side effects, recovery, or return behavior.

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 front-loaded sentence with no wasted words. It immediately communicates the core operation.

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 and the schema plus annotations cover parameter meaning and mutation safety. However, the description is quite thin for a destructive mutation and does not provide usage context or error/return expectations.

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 schema already documents board_id, card_id, task, and done. The description only reinforces the singular task scope and does not add syntax, default behavior, or validation details beyond the schema.

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 states a specific action and resource: ticking or unticking one task in a to-do list. It is clearer than a tautology and distinguishes itself from list/board tools, but it does not explicitly contrast with sibling task mutations such as add_todo_list or move_card.

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 implies use for changing a task's completion state, but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not say when to use this versus other task or board editing tools.

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