wordpress_create_page

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and lists parameters, but does not describe side effects, permission requirements, error behavior, or implications of using the 'status' parameter. It lacks transparency about what happens on creation beyond returning details.

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 well-structured with an 'Args' section and 'Returns' section, making it easy to scan. It lists each parameter succinctly with brief clarifications. No unnecessary filler, though it largely restates the schema which is acceptable given the need for context.

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's complexity with 10 parameters and no annotations, the description covers all parameters and mentions return details. The presence of an output schema also covers return structure. However, it does not address potential error conditions or prerequisites, which would enhance completeness for a mutation tool.

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?

The description adds meaningful explanations beyond the schema's basic names, such as clarifying content format ('HTML or block format'), enumerating status values, and specifying 'Menu order' and 'Publication date (ISO 8601)'. Even though schema coverage is 0%, the description compensates well by covering all parameters with useful context.

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's purpose with a specific verb and resource: 'Create a new WordPress page.' This distinguishes it from siblings like wordpress_create_post and wordpress_create_comment, as it explicitly targets pages.

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 gives no explicit guidance on when to use this tool versus alternatives such as wordpress_create_post. It implies usage for page creation but does not state exclusions or conditions, leaving the agent to infer context from the tool name and siblings.

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