confluence_create_page

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

Annotations already indicate mutability (readOnlyHint=false) and non-destructiveness (destructiveHint=false). The description adds the requirement that body must be in XHTML format, which is useful. No contradictions with annotations.

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?

Two sentences, no filler. Front-loaded with the action. Every sentence adds value: one for the main purpose, one for the body format and parent_id hint.

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 4 parameters and an output schema, the description covers only two parameters in detail. It omits space_key and title, which are required. The body format requirement is included, but not enough for a complete understanding without schema inspection.

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 adds context for 'body' (XHTML format) and 'parent_id' (child page creation), which the schema descriptions already provide. However, space_key and title are not mentioned, and schema description coverage is 0%, so the description partially compensates but misses essential parameters.

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 the tool creates a new Confluence page, which distinguishes it from siblings like 'get_page' or 'update_page'. However, it could be more specific about the scope (e.g., specifying space and parent), but the verb+resource 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 provides a tip about using parent_id for child pages but offers no explicit guidance on when to use this tool versus alternatives like 'update_page' or 'get_page'. No when-not or context for choosing between tools.

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