create-page

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

The description contradicts idempotentHint annotation: it states that calling with an existing title fails, so the tool is not idempotent, but the annotation asserts idempotentHint=true. This is a serious inconsistency.

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, front-loaded with core purpose, no fluff. Every phrase earns its place.

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 no output schema, it describes return values (title, page ID, first revision ID). Includes failure condition, optional parameter purpose, and chaining strategy. Provides complete context for a creation tool.

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 coverage is 100%, and the description adds extra context: contentModel selects non-default formats, comment is a reason, and chaining pattern. It goes beyond schema bare bones.

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 with provided content and returns identifiers. It distinguishes from update-page for existing pages, making the purpose unambiguous.

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?

Explicitly says it fails if page exists, advises using update-page for that case. Also covers contentModel and chaining with update-page for large pages, providing clear guidance on when to use and alternatives.

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