wordpress_update_page

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

With no annotations provided, the description carries the full burden but fails to disclose critical behavioral details: whether updates are partial (PATCH-like) or full replacement, authentication requirements, potential side effects, or the return value structure.

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?

Efficient two-sentence structure with information front-loaded, though the '[UNIFIED]' prefix adds noise without semantic value.

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 mutation tool with 7 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It lacks required parameter explanations, behavioral constraints, and success/failure indicators.

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%, requiring heavy compensation. While the description lists five updatable fields (title, content, status, slug, parent), it completely omits the two required parameters (site, page_id) and provides no format guidance (e.g., whether status accepts 'draft' or 'publish').

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 ('Update') with a specific resource ('WordPress page'), clearly distinguishing it from sibling tools like wordpress_create_page, wordpress_delete_page, and wordpress_update_post.

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?

No explicit guidance on when to use versus alternatives (e.g., wordpress_update_post), prerequisites (requires existing page_id), or when partial updates are preferred over full content replacement.

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