confluence_create_page

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

With no annotations, the description bears full burden. It discloses the Markdown-to-ADF conversion, the return format (ADF JSON), and the image placeholder mechanism. It does not cover permissions or error states, but the key behaviors are conveyed.

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 a single, efficient paragraph that covers purpose, format constraints, and key behaviors without redundancy. Every sentence adds value, and it remains concise despite the tool's complexity.

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 complex tool with nested objects and no output schema, the description addresses the most critical aspects (conversion, image embedding). It omits validation or error handling but effectively complements the parameter schema.

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 coverage is 100%, but the description adds significant meaning: details on image embedding with placeholders and the Markdown conversion. This goes beyond the schema's property descriptions, compensating for the baseline of 3.

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 explicitly states 'Create a new Confluence page' with details on content format (Markdown) and includes what not to do (pass HTML or hand-written ADF). It clearly distinguishes from sibling tools like update, making the purpose unambiguous.

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 provides clear usage guidance on acceptable input formats (Markdown) and warns against incorrect formats (HTML or ADF). It implicitly specifies creation versus update, but lacks explicit when-not-to-use or alternative tool references.

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