create-page

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

With no annotations, the description carries the behavioral burden. It discloses a key behavior: the page must not already exist, implying the operation will fail or reject if it does. It also mentions the content format (wikitext). It does not detail auth requirements or return behavior, but for a create operation, the precondition is the most critical context and is well covered.

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 the primary action and immediately followed by the critical constraint and alternative. No fluff; every word 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?

The schema covers all parameters fully, and the description covers the central behavioral constraint and usage guidance. It lacks an explicit statement of return values or error handling, but given the simple create operation and full schema coverage, the provided context is sufficient for selecting and calling the tool correctly.

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 baseline is 3. The description adds minimal parameter nuance: "wikitext" clarifies the content field, and "must not already exist" relates to the title. This is slight but doesn't substantially exceed what the schema already provides.

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 action: "Create a new wiki page with wikitext content." It names the resource (wiki page), the verb (create), and the content format (wikitext). It also distinguishes itself from sibling by explicitly saying "use update-page to modify existing pages," which removes ambiguity.

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 versus an alternative: "The page must not already exist — use update-page to modify existing pages." This gives a clear precondition and points to the sibling tool for existing pages, providing strong usage direction.

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