wordpress_set_seo_meta

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

No annotations are provided, so the description carries full burden. It states 'Set' implying a write/mutation operation but doesn't disclose behavioral traits like required permissions, whether it overwrites existing metadata, error conditions, or compatibility details beyond plugin names. This leaves significant gaps for a mutation tool.

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 a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes relevant compatibility details without unnecessary elaboration.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks parameter explanations, behavioral context (e.g., effects, errors), and doesn't mention what SEO metadata fields are set (e.g., title, description). The compatibility note adds some value but doesn't suffice for adequate completeness.

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 provides no information about the single parameter 'postId'. It doesn't explain what 'postId' represents (e.g., WordPress post ID), its format, or how to obtain it. With low coverage, the description fails to compensate for the lack of schema details.

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 ('Set') and resource ('SEO metadata') with specificity about compatible plugins (Yoast SEO, Rank Math, All-in-One SEO). It distinguishes from siblings like 'wordpress_analyze_seo' (analysis vs. setting) and 'wordpress_set_custom_meta' (general vs. SEO-specific), though it doesn't explicitly mention these distinctions.

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 guidance is provided on when to use this tool versus alternatives like 'wordpress_set_custom_meta' for non-SEO metadata or 'wordpress_set_og_tags'/'wordpress_set_twitter_cards' for specific SEO aspects. The description implies usage for SEO metadata but lacks explicit context or exclusions.

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