update-confluence-page

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

The description discloses automatic version fetching to prevent conflicts, which is a key behavioral trait. However, it does not mention permissions, return value, or whether updates are partial or full replacements.

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 concise sentences, front-loaded with the main action. No redundant information.

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?

The description covers version handling but omits return value, error conditions, idempotency, and content format. For a mutation tool with 4 parameters and no output schema, this is insufficient for autonomous agent use.

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 the 'version' parameter has additional context about auto-fetching. Other parameters (page_id, title, content) lack any description beyond their names, and the schema provides no descriptions for them. The agent gets no guidance on content format or expected values.

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 'Update an existing Confluence page', using a specific verb and resource. It distinguishes from siblings like create-confluence-page, though it doesn't explicitly contrast with them.

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?

No guidance on when to use this tool versus alternatives (e.g., create-confluence-page, comment-confluence-page). No prerequisites or exclusions are mentioned.

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