wp_update_draft_page

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

No annotations provided, so description carries full burden. It discloses the non-publication behavior and draft-creation fallback, but lacks details on side effects, required permissions, return value, or state changes. Some useful behavioral context, but incomplete.

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?

Two sentences, no wasted words, front-loaded with key purpose and special behavior. Efficient and well-structured for a tool description.

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 6 parameters, no output schema, no annotations, the description is too brief. It does not explain what the parameters do, what the response contains, or any prerequisites (e.g., page must exist). Incomplete for an update tool with moderate complexity.

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 has 6 parameters with 0% description coverage, and the description provides no additional meaning for any parameter. Parameters like 'content' and 'excerpt' are not explained. The description fails to compensate for the lack of schema documentation.

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 it updates an existing draft page, with special handling for published pages (creates new draft). It distinguishes from siblings like wp_update_draft_post (for posts) and wp_create_draft_page (create vs update). The verb 'Update' and resource 'draft page' are specific.

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 explicitly says 'If page is published, creates a new draft instead. Never publishes.' This provides clear context on when to use (for draft pages) and behavior for published pages. However, no explicit when-not-to-use or alternatives are mentioned, but it's well implied.

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