wp_set_seo

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

With no annotations provided, the description carries full burden. It discloses that changes are written to the active SEO plugin, verified by readback, default dry_run behavior (preview only), and the allow_prod guard for production. No contradictions with annotations.

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 concise and well-structured, covering essential details in two sentences. It front-loads the purpose and then efficiently conveys behavioral nuances 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 lacking an output schema, the description provides sufficient context for correct usage: what is affected (SEO meta), how changes are applied (via specified plugin), safety defaults, and required transport. It answers the key questions an agent would have.

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 0%, so the description must compensate. It explains the purpose of all parameters: title, description, canonical, noindex are SEO fields; post_id and install are context; dry_run and allow_prod define behavior. It also clarifies that omitted fields are left unchanged, adding meaning beyond the raw schema.

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 tool's function: setting a page/post's SEO meta (title/description/canonical/noindex). It is distinct from sibling tools like wp_get_seo, making its purpose unambiguous.

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 implicitly indicates when to use it (when SEO meta needs to be set) and provides critical usage constraints (dry_run default, allow_prod requirement, REST transport). It sufficiently differentiates from alternatives like wp_get_seo by contrast of action.

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