Create Page

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

Annotations only include destructiveHint: false, which correctly signals this is not destructive. The description adds little behavioral context beyond 'create' — it does not disclose that pages may be visible immediately, that permissions may govern creation, that Live Doc subtype is cloud-only (though schema says it), or what happens with duplicate titles. With weak annotations, the description carries some burden and only partially meets it.

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 one short, direct sentence: 'Create a new Confluence page.' It is concise and front-loaded. It earns its place but is almost too minimal, providing no extra context beyond the title.

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 12 parameters, a rich schema, and an output schema, the description is not required to explain return values or parameters. However, it lacks guidance on when to use this tool versus create_page_from_template or copy_page, and lacks notes on prerequisites like space existence and permissions. It is minimally viable but not complete.

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 schema already thoroughly documents every parameter. The description itself adds no additional parameter meaning. Baseline 3 is appropriate because the schema does the heavy lifting; the description does not need to repeat it.

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 states a specific verb and resource: 'Create a new Confluence page.' It is clear and distinguishes from siblings like update_page or delete_page. It could be slightly improved by noting it creates a standalone page (vs create_page_from_template or copy_page), but the core purpose is clear.

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 when-to-use guidance or mention alternatives. However, the schema gives substantial context, including mutually exclusive content vs content_file and format options. Sibling names imply alternatives like create_page_from_template, but the description itself does not state when to choose this over those. This is a moderate gap.

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