wordpress_update_post_seo

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

With no annotations provided, the description should fully disclose behavioral traits. It mentions the tool updates metadata and requires a plugin, but does not state whether the operation is destructive, idempotent, or what error conditions apply (e.g., missing plugin).

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 two sentences: one for purpose and one for key features. It is front-loaded with the verb and resource, and every sentence earns its place without redundancy.

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?

Despite 14 parameters and no output schema or annotations, the description provides minimal contextual information. It omits return values, error handling, and how to effectively use the many optional fields, making it incomplete for an agent.

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?

The schema has 0% description coverage for 14 parameters. The description only generically says 'Supports both Rank Math and Yoast SEO fields' without explaining which parameters correspond to which fields or adding semantic meaning beyond the parameter names.

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 action (Update SEO metadata) and resource (WordPress post or page). It distinguishes from sibling tools by specifying support for both Rank Math and Yoast SEO and automatic plugin detection, which differentiates it from general update_post or get_post_seo.

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 mentions a prerequisite (SEO API Bridge plugin) and implies usage for SEO metadata updates only, but it lacks explicit guidance on when to use this tool versus alternatives like wordpress_update_post for non-SEO updates or wordpress_update_product_seo for products.

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