Generate SEO meta + schema

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

No annotations are provided, so the description must carry full disclosure. It mentions returning warnings and a ready-to-paste head block, but it does not clarify whether the tool modifies existing data, its idempotency, required permissions, or potential side effects. The phrase 'Keep page JSON clean' is ambiguous.

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?

Two sentences, front-loaded with the core purpose. Uses technical terms appropriately but is concise. A slight improvement would be breaking into bullet points for readability.

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 the complexity of SEO (multiple tags, schema types, warnings), and no output schema, the description should detail the return structure, field behavior, and example usage. It mentions warnings and head block but is incomplete for a tool of this scope.

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% (single 'seo' parameter with descriptive fields). The description adds context about the output but does not clarify the meaning or constraints of individual fields beyond the schema's existing documentation. Baseline 3 is 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?

The description clearly states it produces an 'SEO sidecar' including meta title/description, slug, robots, canonical, Open Graph, Twitter tags, JSON-LD schema, and a head block. This specific verb+resource combination distinguishes it from siblings like build_page or validate_blueprint.

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 advises to 'apply this at the WordPress/SEO-plugin level' implying it is for final output, but it does not explicitly state when to use this tool versus alternatives like build_page. There is partial guidance but no clear exclusions or alternatives.

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