create-page

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

The description adds behavioral details beyond annotations, such as the failure condition when the page already exists and the return values. It does not contradict annotations; the idempotentHint=true is consistent (failing on duplicate is still idempotent). However, it could mention authentication or rate limits, but annotations already provide safety hints.

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 four sentences, front-loaded with the primary action and return information. Every sentence adds necessary context without redundancy, making it concise and well-structured.

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?

Despite lacking an output schema, the description fully explains what is returned (title, page ID, revision ID) and the failure condition. For a creation tool, this is complete and adequately informs the agent of the tool's behavior.

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?

With 100% schema coverage, the baseline is 3. The description enhances parameter understanding by giving examples for contentModel (e.g., javascript, css) and explaining its default behavior, adding value beyond the schema definitions.

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 it creates a new wiki page and specifies the returned values (title, page ID, first revision ID). It distinguishes itself from the sibling update-page by noting that it fails if the page already exists, providing a clear contrast.

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 explicitly states when to use this tool (creating a new page) and when not to (if page exists, use update-page). It also gives guidance on the optional contentModel parameter and suggests pairing with update-page for building large pages, offering clear usage context.

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