Set SEO title and description

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

Annotations already flag destructive and non-idempotent; the description adds real value beyond them, explaining that each supplied field overwrites the stored value, tags/line breaks are stripped, no undo point is recorded, and which capabilities are required. It also describes the return payload (updated, provider, changed).

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?

A dense but front-loaded paragraph starting with the action and plugin precedence; each subsequent clause carries distinct information (overwrite behavior, sanitization, return values, failure modes, permissions, no undo).

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?

Ample for a four-parameter mutation with no output schema: it covers write semantics, plugin selection, error/refusal conditions, auth requirements, and return fields. Nothing an agent needs to invoke it correctly is missing.

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 100%, and every field already documents omitted-vs-empty behavior, so the description adds only the summary that 'only the fields given are written.' That reinforces but does not extend the per-parameter semantics, making the baseline 3 appropriate.

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?

States a concrete verb and resource (set SEO title/meta description/focus keyword) plus the exact plugin precedence (Yoast over Rank Math). Clearly distinguishable from the sibling wp_seo_get, which it names for reading.

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?

Explicitly redirects reading to wp_seo_get and enumerates when the call fails: neither plugin active, All in One SEO as plugin, or an unknown post. It doesn't contrast against wp_update_post for ordinary titles, but the when/when-not framing is otherwise strong.

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