confluence_create_page

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states 'Create a Confluence page' and 'Returns unified fields' but does not disclose side effects (e.g., whether the page is immediately visible), required permissions, or potential errors (e.g., title conflicts). The output 'unified fields' is vague and lacks explanation.

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 very concise with three short sentences. It is front-loaded with the core purpose. However, it omits useful behavioral details that could be included without excessive length, such as the effect of a missing spaceKey or the return value structure.

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 of the Confluence ecosystem with many sibling tools for staging and updating, the description lacks completeness. It does not clarify how this create tool interacts with the staging workflow, nor does it explain what 'unified fields' means. The absence of an output schema is not compensated by the description.

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 input schema covers 100% of parameter descriptions, providing clear definitions for title, bodyStorageValue, spaceKey, and parentId. The description adds minimal additional meaning beyond the schema, only mentioning that parentId is optional. This meets the baseline but does not compensate for gaps since there are none.

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 Confluence page and mentions the optional parentId. The verb 'create' and resource 'page' are specific. However, it does not elaborate on what type of page (e.g., wiki page, blog post) or distinguish from similar sibling tools like `confluence_update_page`, but this is partially captured by the tool name.

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 (e.g., `confluence_stage_page_update` or `confluence_update_page`). It does not specify prerequisites, such as needing the Confluence space key or handling duplicates. No when-not-to-use information is given.

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