wp_seo_generate_metadata

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether generated metadata is persisted to the site, whether it overwrites existing metadata, what permissions are required, or what the return value looks like. 'Generate' is ambiguous: it could return suggestions or mutate stored content.

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 filler, and the core capability is front-loaded. It does not bury the action or include redundant restatements.

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?

Given that there are no annotations, no output schema, and a complex sibling landscape, the description is too thin. It lacks usage context, behavioral disclosure, and any routing information against similarly named SEO tools, leaving the agent under-informed for correct invocation.

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 single parameter 'site' has 100% schema description coverage, so the schema itself explains its purpose and conditional requirement. The description adds no parameter meaning beyond the schema, which yields a baseline score of 3 when schema coverage is high.

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 states a specific verb and resource ('Generate SEO-optimized metadata') and lists the produced artifacts (title tags, meta descriptions, OpenGraph, Twitter Card data). However, it does not distinguish itself from the sibling tool wp_seo_bulk_update_metadata, leaving ambiguity about when each applies.

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?

There is no guidance on when to use this tool versus alternatives such as wp_seo_bulk_update_metadata, wp_seo_analyze_content, or wp_seo_site_audit. The description provides only a static capability statement with no contextual triggers or exclusions.

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