wordpress_update_post

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

No annotations provided, so description carries full disclosure burden. While 'Update' implies mutation, the description fails to specify idempotency, whether omitted fields are preserved or deleted, authentication requirements, or rate limits. Only 'Can update any field' hints at partial-update capability.

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?

Compact two-sentence structure with action front-loaded. However, the '[UNIFIED]' prefix appears to be metadata leakage or internal labeling that provides no value to the agent.

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?

Inadequate for a 10-parameter mutation tool with 0% schema coverage and no annotations. Missing crucial details: required fields explanation, status enum values, response format/confirmation, and field preservation semantics.

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 coverage is 0%, so description must compensate. It lists only 5 of 10 parameters (missing site, post_id, slug, excerpt, featured_media) and provides no semantic guidance on formats (e.g., comma-separated IDs for categories/tags, valid status enum values like 'publish' vs 'draft').

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?

Clear verb 'Update' with resource 'WordPress post'. The word 'existing' distinguishes from create operations. However, it fails to differentiate from sibling tools like wordpress_update_post_seo or wordpress_advanced_bulk_update_posts, which could cause selection ambiguity.

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 this versus alternatives, no prerequisites mentioned (e.g., needing post_id from a previous search), and no warnings about when not to use (e.g., vs. bulk operations for multiple posts).

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