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

Annotations declare write/non-destructive/openWorld=false, so the safety profile is already covered. The description adds the non-obvious behavioral fact that this is a wholesale replacement and that omitting fields is not allowed ('Send every content field back'). It does not mention permissions or the response shape, 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 tight sentences with the mutation and the full-replacement rule front-loaded. No filler, though the second sentence is terse enough to feel clipped rather than instructive.

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?

A write tool with no output schema, 0% schema coverage, and a required nested object demands more than two sentences. The description covers the replacement contract but leaves all identifier parameters and the required content fields undocumented, so an agent cannot call it confidently without opening the schema.

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% and there are 4 required params plus an 8-field nested content object. The description only gestures at the content object ('every content field') and says nothing about projectId, siteId, or improvementId, so it does not compensate for the documentation gap.

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 and resource: 'Replace the drafted content of an improvement.' The phrase 'drafted content' narrows scope to the improvement's editable draft, which separates it from update_article (article body) and from apply/submit/decide improvement siblings. It stops short of explicitly naming which sibling to prefer, but the resource is identifiable.

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?

'Send every content field back' implies this is a full replacement rather than a patch, which is a usage constraint. However, there is no guidance on when to use this versus apply_article_improvement, submit_article_improvement, or generate_article_improvement, 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.