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

The description adds meaningful behavioral detail beyond the annotations: it explicitly says the item is 'marked, never deleted' and that the operation is reversible via `done: false`. This complements idempotentHint and destructiveHint without contradicting them.

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 compact and well-structured: trigger conditions first, then parameter mechanics, then reversibility. Every sentence earns its place and there is no redundant or vague wording.

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 simple two-parameter toggle tool, the description covers the trigger, the id source, the `done` flag behavior, and the safety guarantee. No output schema is present, but the outcome is sufficiently implied by 'the item is marked'.

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%, and the description essentially restates the schema's parameter info: `id` comes from connections_todo_list and `done: false` reopens. It adds no deeper semantics beyond what the input schema already provides, so the baseline score of 3 applies.

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 tool's action: checking a to-do off or reopening it based on the member's report. It names the resource (a to-do identified by `id`) and distinguishes itself from sibling tools like connections_todo_add and connections_todo_list by focusing on the completion/reopen action.

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 gives explicit positive usage triggers ('done, finished, completed, handled - or should be reopened') and specifies that the correct `id` comes from connections_todo_list. However, it does not explicitly state when NOT to use this tool, such as for adding new to-dos, so it stops short of full when/when-not coverage.

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