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

Adds real context beyond the destructiveHint annotation: 'The description accepts Markdown and replaces the card's whole page' concretely explains the destructive nature for the description field, and 'null clears a date, the repeat or the cover' explains clearing semantics. It does not address whether unmentioned fields are preserved, leaving some behavioral gaps.

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?

Three tight sentences, front-loaded with the field list followed by two sentences of important caveats (Markdown/last-write, null clearing). No filler; nearly every clause carries information.

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 an 8-param mutation tool with no output schema, the description covers fields, null semantics, and page replacement well, but omits the partial-vs-full update behavior (are unspecified fields kept?) and any return/error expectations. Adequate but with a notable gap given the parameter count.

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 63%; the schema already documents dueDate, startDate, coverColor, recurrence, and coverImageAttachmentId. The description usefully clarifies the two cover params ('a color, or one of the task's image attachments') and adds meaning to the undocumented `description` param, but title and cardId remain unexplained, so it only partially compensates.

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?

States a specific verb ('Edits') and resource ('a task') and enumerates the editable fields (title, description, due date, start date, repeat, cover). This implicitly distinguishes it from label/assignee/field tools, but it never explicitly names a sibling alternative, so it stops 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?

Usage is only implied by the field list - an agent can infer this is the general task-editing tool. There is no explicit when-to-use versus set_task_field, set_task_labels, move_task, or complete_task, and no stated prerequisites.

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