Create a page

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

Annotations only carry idempotentHint=false, so the description bears the behavioral disclosure burden. It discloses the PageDuplicateCreate failure mode for duplicate paths and clarifies that the editor determines content interpretation. It does not go further into permissions, side effects, or response shape, but it reveals the most important non-obvious behavior.

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?

Three sentences, front-loaded with the core purpose, and every sentence adds discriminating information: creation, duplicate-path behavior with an explicit alternative tool, and editor semantics. There is no filler or redundancy.

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?

For a create operation with nine parameters and no output schema, the description covers the essential invocation decision: when to create versus update, and how to interpret content via the editor field. The remaining parameter details live in the schema, and no critical selection or invocation context is obviously missing.

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 high at 78%, so the baseline is already strong. The description adds meaning beyond the schema by explaining that the editor controls how content is interpreted and that markdown source must set editor="markdown". This is genuinely useful for choosing the right parameter value.

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 opens with a specific verb and resource ('Creates a page') and immediately distinguishes the tool from its sibling update_page. The purpose is unambiguous and differentiated from the large sibling set.

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 provides explicit usage conditions: the path must not already exist in the locale, otherwise update_page should be used for existing pages. It also tells the agent when the editor parameter matters, giving clear decision-relevant guidance.

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