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

Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so the description's job is extra context. It delivers the key one: passing "" clears/removes a field, which is precisely the behavior behind the destructive hint. It does not state partial-update semantics (only supplied fields change) or what happens to omitted fields, keeping it short of a 5.

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, zero filler, with the operation stated first and the non-obvious edge case (empty string = removal) immediately after. Nothing repeats the title or wastes tokens.

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 an output schema present and full schema description coverage, the description need not explain return values, and annotations cover safety. What remains thin is mutation contract detail — whether providing no optional fields is an error and whether the operation is a partial or full replace — but the essentials for calling it correctly are present.

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 100%, including the '"" to remove the tag' note, so the schema already documents all four parameters. The description restates the tag empty-string convention rather than adding new semantics (e.g., whether at least one of title/description/tag must be supplied), so baseline 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?

Clear verb+resource plus the specific mutation surface ('title, description, or tag'), which implicitly separates it from siblings like move_task or complete_task. However, it never names a sibling or explicitly excludes the other task-mutating tools, so an agent must infer the boundary.

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 implied by the field list — edit a task's text fields here, use move_task/complete_task for other changes — but no explicit when-to-use or when-not-to-use guidance is given. The one concrete directive (empty string removes the tag) is operational, not a selection rule.

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