wordpress_get_post_seo

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

No annotations provided, so description carries full burden. It compensates partially by detailing return values (focus keyword, meta title, social settings) since no output schema exists. However, it omits safety confirmation (read-only status), error behaviors (missing post ID, inactive plugin), or rate limiting information.

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?

Generally well-structured with logical flow: action → return values → prerequisites. The '[UNIFIED]' prefix wastes space without adding semantic value, but the remaining three sentences are dense with necessary information.

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?

Without an output schema, the description adequately documents return fields. However, with zero schema parameter coverage and two required parameters, the failure to document inputs leaves significant gaps. Sibling differentiation is implicit rather than explicit.

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% with no property descriptions. The description fails to compensate by explaining what 'site' expects (domain, ID, or slug?) or confirming 'post_id' is the WordPress post identifier. Zero parameter guidance provided.

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?

Excellent specificity: 'Get SEO metadata' clearly identifies the action and resource. Explicitly distinguishes from siblings by specifying 'post or page' (vs. wordpress_get_product_seo) and 'Get' (vs. wordpress_update_post_seo), and clarifies it retrieves Rank Math/Yoast fields rather than general post content (vs. wordpress_get_post).

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?

Provides critical prerequisite 'Requires SEO API Bridge plugin' which functions as a when-not-to-use constraint. However, lacks explicit guidance on choosing between this and wordpress_get_product_seo or when to use the update variant instead.

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