Confluence Create Page

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

With zero annotations, the full burden falls on the description. It discloses the input format (markdown) and the post-creation side effect ('return it re-read'), but omits permission conditions, failure handling for duplicate titles, or any reversibility considerations.

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 that places the action first, then the input format, then the distinctive behavior. Every word contributes; no fluff or redundant restatement of the schema.

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 schema fully documents the four parameters and an output schema exists, so the description focuses on non-schema information: markdown conversion and a verify-by-reread step. For this straightforward create operation, this is enough to call, though it leaves permission and failure handling unstated.

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%, so the baseline is 3. The phrase 'from markdown' merely mirrors the existing `body` schema description, and no additional meaning is added for space_key, title, or parent_id.

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 the precise verb 'create a markdown page from markdown' and appends a distinctive behavior, 'return it re-read,' which differentiates it from siblings like `confluence_update_page` or `confluence_get_page`.

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 wording about when to choose create over update, when a page already exists, or what prerequisites to establish (such as an existing space_key). The description says only the tool's name and parameter list imply the usage.

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