confluence_create_page

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

No annotations provided, and description merely says 'Create' without disclosing behavioral traits like required permissions, idempotency, error handling, or what happens if the page already exists.

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?

Single sentence is concise but could be slightly expanded to mention required parameters (spaceKey, title, body) without being verbose.

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 it's a creation tool with 4 parameters and no output schema, the description lacks crucial details like return value (e.g., page ID), error states, and prerequisites (e.g., space must exist).

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?

Input schema covers all 4 parameters with descriptions (100% coverage). The description adds no extra meaning beyond the schema, resulting in a baseline score of 3.

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?

Clearly states 'Create a new page in Confluence', providing the verb and resource. However, it does not differentiate from sibling tools like 'confluence_create_page_in_personal_space' or specify that pages are created in regular spaces.

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?

No guidance on when to use this tool versus alternatives (e.g., for personal spaces or updates). Lacks context about prerequisites or when not to use.

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