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

Annotations already flag destructive=true and idempotent=false, but the description adds genuinely new behavior: full rewrites and large removals are gated by the collaborative editor, removals require an explicit allowRemoval flag, and conflicts require re-reading with requestId preserved on retry. That conflict/retry semantics is exactly the context annotations cannot convey.

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?

Six tight sentences, front-loaded with the core action and preference order, then the safety gate, then conflict handling. No filler or repetition; each sentence carries an actionable rule.

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 rich annotations, the description only needs to supply operational caveats, and it does: read-first prerequisite, edit-preference, removal gate, and conflict/retry protocol. An agent has everything needed to call this correctly on the first attempt.

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%, so the schema already documents id, edits, requestId, and allowRemoval in detail. The description reinforces allowRemoval's condition and requestId reuse on retries, but largely echoes what the schema states, so the 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?

States a specific verb (apply targeted Markdown edits) and an unambiguous resource (a task), with the constraint that it operates on existing content after a read. This cleanly separates it from edit_doc_content, which targets a different resource, without needing to name the sibling.

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?

Gives clear preconditions and preferences: read current content first, prefer exact text or block edits, set allowRemoval only for user-requested removals, and re-read after a conflict rather than retrying blindly. It lacks an explicit 'when to use this vs update_task / edit_doc_content' routing statement, so it falls short of a 5.

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