edit_confluence_page

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

No annotations are provided, so the description carries full burden. It discloses version auto-increment and Mermaid diagram limitations, but does not mention required permissions, destructiveness, or response characteristics. The information is partially transparent but lacks completeness.

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 front-loaded with a clear first sentence, but then includes a lengthy section on Mermaid diagrams that, while useful, adds verbosity. The structure could be more compact, but the key information is present.

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?

Given the complexity of 4 parameters and no annotations, the description lacks completeness. It omits content format details, version handling beyond auto-increment, and any mention of the return value (though an output schema exists). The Mermaid section provides niche context but does not compensate for overall gaps.

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?

With 0% schema description coverage, the description must explain parameters. It only covers version (auto-increment) and provides Mermaid-specific content guidelines. It does not describe the meaning of page_id, title, or the expected format of content (e.g., HTML or Confluence storage format). This leaves significant ambiguity.

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 'Updates a Confluence page,' specifying the verb and resource. It distinguishes from sibling tools like confluence_create_page and confluence_delete_page, but could be more explicit about which fields are updated.

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 description mentions automatic version increment but does not provide explicit guidance on when to use this tool versus alternatives like confluence_create_page or confluence_delete_page. It only lightly implies usage context.

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