wp_create_draft_page

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool creates drafts only and never publishes, which is key. However, it lacks details on permissions, error behavior, or what happens on duplicate titles, leaving gaps.

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 concise sentence with no waste, front-loading key information. However, it is slightly underspecified for the tool's complexity, balancing conciseness with 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 has 5 parameters, 1 required, no output schema, and no annotations, the description is incomplete. It omits parameter semantics, return values, and potential side effects, leaving significant gaps for an AI agent to use correctly.

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%, and the description does not elaborate on any of the 5 parameters (slug, title, parent, content, excerpt). It adds no meaning beyond the schema, failing to compensate for the lack of property descriptions.

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 verb 'Create' and the resource 'page', specifies it's a draft only and never publishes, effectively distinguishing it from siblings like wp_create_draft_post (post vs page) and wp_update_draft_page (update vs create).

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 includes explicit constraints ('DRAFT only', 'Never publishes', 'Staging only'), giving clear context for when to use. However, it does not explicitly mention alternatives or when not to use, though the constraints imply exclusions.

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