wordpress_update_post_seo

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

With no annotations provided, the description carries the full burden. It discloses the auto-detection behavior for plugins but fails to specify mutation characteristics (partial vs. full update), error handling when no SEO plugin is active, or 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?

Four sentences efficiently convey purpose, compatibility, behavior, and prerequisites. The '[UNIFIED]' prefix is slightly unnecessary metadata but does not significantly detract from the front-loaded 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 14-parameter mutation tool with no output schema, the description adequately covers the external dependency (Bridge plugin) but lacks explanation of parameter patterns (all optional except site/post_id) and expected response format.

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 compensate by explaining any of the 12 optional parameters (e.g., whether null values skip updates or clear fields). It mentions supported field types conceptually but not their specific semantics.

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 specific action ('Update SEO metadata') and target resource ('WordPress post or page'), distinguishing it from the sibling 'wordpress_update_product_seo' tool through explicit scope limitation.

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 provides a critical prerequisite ('Requires SEO API Bridge plugin') and clarifies plugin compatibility ('Supports both Rank Math and Yoast'), but does not explicitly direct users to the product-specific SEO tool for WooCommerce products.

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