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

Annotations provide only idempotentHint, so the description carries most of the behavioral burden. 'Experts are not emailed' is a genuinely useful side-effect disclosure absent from structured data, but the description says nothing about permissions required, whether closing is reversible, or effects on dependent tasks.

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?

Eleven words, front-loaded with the state semantics and ending with the notification caveat; every clause earns its place with no filler.

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 state-change tool with no output schema, the description covers enum semantics and one side effect, which is adequate but leaves reversible-ness and permission requirements unstated for a mutation operation.

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%, so the description must compensate. It does add real meaning for the 'status' enum values, which the schema lists without explanation, but the required 'taskId' identifier is never described.

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 specifies what the two status values do ('closed ends the task, draft pauses it'), which is the substantive purpose beyond the tautological name. It does not differentiate itself from siblings like update_task or publish_task, so it falls short of a 5.

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?

Choosing between 'closed' and 'draft' is implied by the definitions of each value, but there is no guidance on when to prefer close_task over update_task or publish_task, and no stated prerequisites or exclusions.

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