confluence_create_page

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does reveal that the body is treated as Confluence storage-format XHTML, which is a non-obvious behavioral trait. However, it omits other useful behaviors like return value, error handling, or permission requirements, leaving those to the agent's inference.

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, with the core purpose front-loaded. Every word earns its place; there is no redundancy or filler.

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 tool has 4 parameters, no output schema, and no annotations. The description covers the core action and the body format caveat, but it lacks guidance on return values, error conditions, prerequisites (e.g., space existence), and when to use create vs update. It is minimally adequate but leaves several usage questions unanswered.

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 75% (3 of 4 params have descriptions). The description adds a small clarification about body format ('pass HTML-ish markup, not markdown') that goes slightly beyond the schema's body description, but it does not add meaning for title, spaceKey, or parentId. Overall, the schema does most of the heavy lifting.

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 opens with 'Create a new Confluence page'—a specific verb+resource that clearly distinguishes this tool from sibling tools like confluence_update_page, confluence_search, and confluence_get_page. The additional note about body format reinforces the purpose by clarifying what kind of content is expected.

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 implies usage for creating pages but provides no explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. The body format note is more about parameter usage than tool selection, so it does not fully address how this tool fits relative to siblings.

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