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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the mutation profile is covered. The description adds genuinely new context: the edit produces a saved new version and returns it, which clarifies the effect on the original beyond what the hints say. It stops short of describing rate limits, permissions, or what happens to the prior version.

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?

Front-loaded trigger sentence, then a compact enumeration of edit types, then the versioning fact and the alternative tool. No filler sentences; every clause earns its place.

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 format need not be explained, and the description still notes that a new version is returned. With annotations covering safety and the schema covering params, the definition gives everything needed to select and call this tool correctly.

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% with only two params (artifactId, instruction), and the schema already gives usage examples for both. The description adds no parameter-level detail, so the baseline 3 applies — the schema carries the load.

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 ('edit a saved Xenition item') and enumerates the concrete operations covered (rewrite, shorten, expand, tone, grammar, translate). It also names the sibling it is not (review_artifact), so an agent can separate them without opening a 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?

Opens with an explicit trigger ('when the user wants one of their existing items changed in place') and closes with an explicit exclusion plus alternative ('To only suggest changes without editing, use review_artifact'). Both when-to-use and when-not-to-use are given.

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