wp_create_page

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

With no annotations, the description carries the full burden for behavioral disclosure. It does reveal that dry-run previews are supported, which is useful and not obvious from the function name. However, it does not disclose side effects of actual creation, required authorization, default behavior, or what happens on success or failure.

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 with no filler. The core purpose is front-loaded, and the dry-run capability is stated efficiently. Every word contributes meaningful 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 creation tool with 12 parameters, no output schema, and no annotations, this description is incomplete. An agent gets no sense of required inputs beyond the schema, what the dry-run preview returns, how mutating the action is, or what a successful creation response looks like. The sparse context leaves important operational 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 only 8% (only dry_run has a description), yet the description does not compensate for the other 11 undocumented parameters. It adds some meaning by mentioning dry-run previews, which maps to the dry_run parameter, but it provides no semantic detail for title, slug, status, content, parent, or other 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 uses a specific verb and resource ('Create a WordPress page'), clearly identifying what the tool does and distinguishing it from sibling tools like wp_create_post. It also adds the non-obvious dry-run preview capability. It is clear, though it does not explicitly contrast itself with other siblings in the description.

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 guidance about when to use this tool versus alternatives such as wp_create_post, wp_update_page, or wp_get_page. There is no mention of exclusions, prerequisites, or when to prefer a sibling tool. The intended use is only implied by the tool's name and basic statement.

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