create_page

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

With no annotations, the description solely must disclose behavioral traits. It only states 'create a new page', which implies mutation but does not specify whether the page is created as a draft or published, authentication needs, rate limits, or behavior on duplicate titles.

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 a single sentence, which is concise but lacks necessary detail. It is not verbose, but the brevity comes at the cost of completeness.

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 the tool complexity (6 parameters, nested objects, no output schema), the description is severely incomplete. It does not explain return values, side effects, or how to use complex parameters like 'meta' and 'builder_payload'.

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 only 17% (only 'site' has a description). The description adds no meaning for the 6 parameters, including the required 'title', optional 'slug', 'content', 'meta' object, and 'builder_payload'. With low coverage, the description fails to compensate.

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 tool creates a new page in WordPress, with a specific verb and resource. It distinguishes from sibling tools like update_page or delete_page, though it does not explicitly differentiate from publish_page regarding draft vs published state.

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?

No guidance on when to use this tool versus alternatives like publish_page or create_template. Missing context about prerequisites, typical use cases, or when not to use it.

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