wp_create_page

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

The description discloses the core side effect (creates a page) and the authentication prerequisite (WP_USERNAME/WP_APP_PASSWORD). However, with no annotations and no output schema, it does not explain default status behavior, whether the page is immediately visible, what happens if credentials are missing, or what the caller receives in response. These are meaningful gaps, though the description is not misleading.

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 two short sentences, front-loads the action and resource, and adds the critical credential requirement with no filler. Every sentence contributes useful information.

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 tool with no annotations, no output schema, and four parameters, the description is underspecified. It omits parameter semantics, response shape, and important defaults such as the resulting page status. The auth note helps, but the description alone is not enough for a caller to invok it correctly in most real contexts.

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 0%, so the description needs to compensate by explaining the parameters. It does not mention title, parent, status, or content at all; it only describes the overall operation and auth requirements. The agent receives no additional meaning beyond raw types and an enum.

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 states a specific action and resource: 'Create a new WordPress page.' This clearly distinguishes it from siblings like wp_create_post by targeting the WordPress 'page' content type rather than a post.

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 use case is clear: the agent should call this when creating a WordPress page. It does not explicitly exclude alternatives such as wp_create_post or wp_update_page, but the action and resource are stated directly, providing clear context without explicit exclusions.

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