Create Page

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

Annotations only include destructiveHint: false, which is minimal. The description 'Create a new Confluence page.' adds no behavioral details beyond what the tool name implies. It does not disclose things like content format handling, mutual exclusivity of content and content_file, or whether the page is immediately published. With such sparse annotations, the description carries the burden and fails to provide meaningful transparency.

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 sentence with no wasted words, which is efficient. However, it is under-specified for a complex tool with 12 parameters. It lacks structure and any additional context, making it minimally viable but not appropriately sized for 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?

Although the schema and output schema provide rich structured information, the description fails to add contextual completeness. It does not mention when to use this tool versus create_page_from_template, nor does it hint at content handling nuances. The tool is a create operation with many options, and the sparse description leaves the agent without key decision-making context.

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 schema covers 100% of the parameters with detailed descriptions, so the baseline is 3. The tool description itself does not add any parameter semantics; it just says 'Create a new Confluence page.' Since schema descriptions are already thorough, the lack of addition is acceptable but not a bonus.

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 uses a specific verb and resource: 'Create a new Confluence page.' This clearly states the action and object. However, it does not distinguish itself from sibling tools like confluence_create_page_from_template, which also creates a page, so it doesn't fully address differentiation.

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 no guidance on when to use this tool versus alternatives such as creating from a template or copying a page. There is no mention of prerequisites, exclusions, or context in which this tool is preferred. The usage must be inferred entirely from the name and schema.

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