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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description goes further by naming the concrete consequence: removing an item also wipes its tick history. It also rules out a feared side effect with "Does not send messages to anyone," which is exactly the kind of context annotations cannot express. It omits whether a call is atomic across the multiple arrays or whether partial application is possible.

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?

Front-loaded with the activation condition, then the operation list, then two short sentences on side effects. The middle sentence is a long enumeration, but every clause maps to a real parameter group, so little is wasted.

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?

With 10 parameters, an output schema, and rich annotations, the description covers purpose, credential, and destructive consequences adequately. The remaining gap is whether the add/edit/remove/mark arrays can be combined in a single call or must be issued separately — a meaningful question for a 10-parameter mutation tool that the description leaves unanswered.

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 every parameter carries its own example and constraints, so the schema does the heavy lifting. The description adds only that ticking/unticking works "by number" and that the link must be the private organizer one — useful framing but not new semantics for individual fields.

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 names a specific resource (a shared checklist page) and enumerates the exact operations: add items, edit text/section/assignee/due, remove, tick/untick by number, rename, change note, close/reopen. This is clearly distinguishable from create_shared_checklist and show_checklist_results, which the agent can rule out without opening a schema.

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?

"Use this when the organizer wants to..." gives a clear activation condition and even identifies the acting role (organizer) plus the required credential (private organizer link). It stops short of explicitly naming siblings as alternatives for the read and create cases, so the routing is implied rather than spelled out.

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