confluence_update_page

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

The description discloses an important side-effect: automatic version increment. However, with no annotations, it does not mention required permissions, behavior if the page does not exist, or whether the body is fully replaced. This leaves several behavioral aspects unexplained.

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?

The description is two concise sentences, front-loaded with the action, and includes the useful versioning side-effect without any waste. Every word contributes to understanding.

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?

For a simple update tool, the description covers the core purpose and a key side-effect, but lacks details about permissions, error handling, and return value. With no output schema or annotations, these omissions mean the description is adequate but not fully complete.

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?

The description adds meaning to the title and body parameters by saying 'title and/or body', indicating they are the updatable fields. However, it does not explain the pageId parameter or provide format constraints (e.g., body markup), and with 0% schema coverage, the description only partially compensates for the lack of parameter documentation.

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 clearly states the action (update), the resource (Confluence page), and the specific fields affected (title and/or body). This distinguishes it from sibling tools like create_page, get_page, and search by specifying the exact mutation scope.

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?

The verb 'update' implies this tool is for modifying existing pages, which differentiates it from create_page, but the description does not explicitly state when to use it versus alternatives or provide exclusions. There is no guidance about prerequisites like the page needing to exist.

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