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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds non-trivial context the annotation cannot: deletion is gated on human intent and is reversible via restore. It still doesn't say what happens to an item's subtasks/needs when an item is deleted, and the key-versioning staleness rule lives only in the schema.

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?

Two sentences, front-loaded with the mutable surface, and the parenthetical on needs is genuinely informative rather than filler. The long comma enumeration partly restates schema parameter names, so it is dense but not wasteful.

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 16-parameter mutation tool with a nested fields object and no output schema, the description plus 88% schema coverage leaves the agent able to call it correctly, and the delete/restore story is covered. Minor gap: no statement of what a successful call returns or confirms, though no output schema exists to lean on.

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 coverage is 88%, so the baseline is 3, but the description adds real gloss the schema doesn't: needs means the item is blocked until those are done, options applies to a question, and "its place in the list" maps to the before/after pair. That semantic framing raises it above baseline.

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?

A concrete verb plus an enumerated list of what can be changed (list, title, section, fields, needs, notes, options, position) and the delete/restore pair. Purpose is unambiguous, but no sibling tool is named, so the boundary with tick/claim/answer/section is only implied by the attribute list.

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?

"delete only when the human asks, or calls the work off, or for a duplicate you made; restore brings it back" gives explicit conditions for the risky operation and its inverse, which is the guidance an agent most needs here. It stops short of saying when to prefer tick/claim/answer instead, which the schema covers but the description does not.

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