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. It accurately describes the creation action without contradictory claims. It does not disclose side effects (e.g., permissions required, overwrite behavior) but is sufficient for a straightforward create operation.

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 concise and well-structured with a clear statement followed by parameter descriptions in a standard Args format. No unnecessary words or repetition.

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 (4 parameters, no output schema, no annotations), the description is fairly complete. It lacks information about the return value (e.g., created page object) and any constraints on the ADF body, but adequately covers creation essentials.

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?

The description provides meaningful explanations for all four parameters beyond the schema, including an example for adf_body. It clarifies space_id as the target space, title as the page title, and parent_id as optional nesting, compensating for the 0% schema coverage.

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 'Create a new Confluence page with ADF content', specifying the verb (Create), resource (Confluence page), and content format (ADF). It effectively distinguishes this from siblings like confluence_edit_page and confluence_push_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?

The description does not provide explicit guidance on when to use this tool versus alternatives like confluence_edit_page (for existing pages) or confluence_push_page. It only implicitly indicates creation, but lacks when-not-to-use or context for selection.

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