confluence_create_page

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

There are no annotations, so the description carries the full burden for behavioral disclosure. It only states that a page is created and does not mention permissions, side effects, response shape, draft behavior, or whether the operation can be safely retried. This is a mutation tool with no safety information in annotations, so the description is thin.

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 concise sentence that is front-loaded with the main action and object. There is no redundant wording or filler, and every word contributes to identifying the tool's purpose.

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?

The tool has five parameters, all covered by the schema, but no output schema and no annotations. The description explains what the tool does but not return values, exclusions, or behavioral context such as permissions or draft semantics. It is adequate for a simple create operation but leaves meaningful gaps.

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 parameters are already well documented. The description adds no parameter-level meaning beyond 'specified space,' which matches the spaceId parameter already described as a numeric space ID. The baseline of 3 is appropriate because the schema does the heavy lifting.

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 ('Create'), a clear resource ('a new Confluence page'), and a scope ('in the specified space'). It is immediately distinguishable from sibling tools like confluence_update_page, confluence_get_page, and confluence_search because 'new page' makes the operation explicit.

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 implicitly signals this tool is for creating pages, but it gives no explicit guidance about when to choose it over alternatives such as confluence_update_page or confluence_add_comment. The schema does reference confluence_get_spaces for ID lookup, but the description itself does not provide when-to-use or when-not-to-use guidance.

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