Get Page Version Diff

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only the output modality ('unified diff'), and says nothing about error behavior for non-existent versions, ordering of from/to, or pagination/size limits on large diffs.

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?

A single front-loaded sentence with zero filler; the core operation is stated immediately with no preamble.

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 a full input schema, an output schema, and rich annotations, the description needs only to identify the operation, which it does. The remaining gap is directional semantics between from_version and to_version plus failure behavior, which is a minor omission rather than a blocking one.

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%: page_id even includes a URL example and both version parameters are documented with minimums. The description adds no additional meaning such as whether from_version must be less than to_version or whether either can reference the current version.

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?

The description names a specific verb (get) and resource (unified diff between two page versions), which is a distinct operation not offered by any sibling such as confluence_get_page or confluence_get_page_history. It does not explicitly route the agent away from those siblings, but the 'diff between two versions' framing is unambiguous.

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?

There is no guidance on when to reach for this versus confluence_get_page_history or confluence_get_page, nor any mention of prerequisites (valid version numbers, read permission, behavior when from_version equals to_version). The use case is inferable from the name but not stated.

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