Create WordPress Page

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

Annotations already indicate a mutating, non-destructive operation. The description adds the key safety behavior that it 'Defaults to status='draft'', and explicitly mentions the response_format option. It also notes the return type as WPContentItem, giving some behavioral insight beyond annotations.

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 concise and well-structured, starting with the purpose, then a bulleted arg list, and a Returns line. There is no redundant fluff; the reference to wp_create_post avoids repeating full parameter definitions.

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?

With no output schema, the description only states 'Returns: The created WPContentItem,' which lacks detail about the returned object's fields. Also, it doesn't address potential errors, permissions, or edge cases like invalid parent IDs. It's adequate for a simple create operation but has clear gaps.

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 groups shared params under 'same as wp_create_post' and explicitly explains parent and menu_order, but this largely duplicates schema information. It adds marginal value via the sibling reference, but not enough to exceed baseline.

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 static page,' specifying a verb and resource. It distinguishes from siblings like wp_create_post (which handles other post types) and wp_update_page/wp_delete_page. The default status='draft' adds clarity.

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?

It provides clear context that this tool creates static pages, and the args reference wp_create_post for shared semantics. However, it doesn't explicitly state when to prefer this over wp_create_post or other alternatives, though the page-specific purpose is evident.

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