create_page

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

With no annotations, the description carries full burden. It discloses meaningful behavioral details: 'type is a KIND ... mapped to the numeric backend type' and warns about empty-title publishing without seo. However, it does not mention possible side effects, permissions, return values, or error conditions, leaving gaps for a mutation tool.

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 core action, and every sentence earns its place. The alternative tool and key caveat are packed efficiently without 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?

The description plus the rich schema (100% coverage, detailed slug/type notes) covers the main invocation concerns. It lacks an explicit return value statement (no output schema), but for a create tool with an empty page and alternative guidance, the provided context is largely complete. Could be improved by noting what is returned.

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 baseline is 3. The description adds beyond schema by explaining that 'type is a KIND' underlying numeric mapping and why 'seo' matters (avoids empty-title publishing), which gives agents extra semantic context not present in the structured fields.

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 'Create a new (empty) page' – a specific verb and resource. It also distinguishes the tool from sibling 'build_page' by noting the empty-page scope, so the purpose is 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?

Explicit guidance is provided: 'For a page with content use build_page instead' names the alternative and gives the condition for using this tool. Additionally, the warning to 'pass seo so it doesn't publish with an empty title' instructs on a prerequisite for safe use.

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