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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description corroborates this with 'Non-destructive: it suggests, it doesn't edit' and adds the useful detail that comments are anchored to quoted passages. It does not address idempotentHint=false or any cost/latency behavior, but with strong annotation coverage that is a minor gap.

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 tightly written sentences: the purpose and output shape come first, the non-destructive constraint and alternative follow. Every clause earns its place with no filler.

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?

Output schema exists, so return values need no explanation, and the description still characterizes the output (quoted-passage-anchored comments on three axes). Combined with the non-destructive statement and the edit_artifact routing, an agent has everything needed to call this 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?

Only one parameter, and schema description coverage is 100% with the schema itself noting 'best for documents'. The description's 'Xenition documents' reinforces the same idea rather than adding format, ID syntax, or scoping detail, so baseline 3 is appropriate.

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 (review), a specific resource (the user's Xenition documents), and the shape of the output (constructive comments tied to quoted passages on clarity, structure, correctness). This clearly separates it from siblings like edit_artifact, summarize_artifact, and extract_from_artifact.

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?

Explicitly routes the agent: it 'suggests, it doesn't edit (use edit_artifact to apply changes)'. That names the alternative and the condition that selects it. It does not, however, distinguish itself from summarize_artifact or query_document, so it stops short of full when/when-not coverage.

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