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

No annotations are provided, so the description carries the full burden. It does disclose two meaningful behaviors: the operation destroys and replaces the entire draft content, and a single large call risks truncation by response length. It does not explain the revision/concurrency semantics (that a new revision is produced, or what happens if revision_id is stale), which is the remaining gap for a mutation tool with zero annotation coverage.

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, front-loaded with the core action before the caveat, and no filler. The second sentence is long but every clause carries actionable routing information; minor trimming of the parenthetical '(дописывание в конец)' would tighten it further.

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?

An output schema exists, so return values need no explanation, and the description covers the destructive nature plus the practical truncation hazard — the two things an agent most needs before calling. What is missing is the revision model: whether this creates a new revision (implied by the created_by parameter) and how a stale revision_id is handled, which matters given sibling tools like revert_artifact and list_artifact_revisions.

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 all four parameters, including the concurrency role of revision_id and the created_by enum. The description only gestures at 'content' via the warning about 'объёмный content' and adds no format or constraint detail beyond the schema, 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 and resource — 'Полностью перезаписать содержимое активного черновика артефакта' — making the full-replacement semantics unmistakable. It also names the two sibling tools that offer a different mode of editing, so an agent can distinguish it from replace_range_in_artifact and replace_substring_in_artifact without opening any schema.

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 an explicit condition that should route the agent away from this tool: for large documents, build incrementally with replace_range_in_artifact (append) or replace_substring_in_artifact instead of rewriting everything in one call. That is a concrete when-not rule with named alternatives, not merely implied usage.

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