wordpress_get_post_seo

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the tool is read-only (despite the 'get' name), any side effects, authentication requirements, or rate limits. The only behavioral detail is the plugin requirement, which is insufficient for a mutation-ambiguous tool.

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 sentence that efficiently conveys the tool's purpose and key details. The '[UNIFIED]' prefix adds minimal value but does not detract significantly. Information is front-loaded with the main verb 'Get' and followed by specific fields.

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 two-parameter input and lack of output schema, the description should explain the return value structure more thoroughly. It lists example fields but does not describe the full response format. It also omits error handling or edge cases (e.g., post not found, plugin missing). The context is insufficient for an AI agent to fully understand the tool's capabilities.

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 input schema has two required parameters (site, post_id) with 0% schema description coverage. The description does not clarify what 'site' means (e.g., URL, site identifier) or what 'post_id' expects (the WordPress post ID). No additional context is provided beyond the parameter names.

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 that this tool retrieves SEO metadata for a WordPress post or page, including specific fields like focus keyword, meta title, description, and social media settings. It distinguishes itself from sibling tools such as wordpress_get_post (which retrieves post content) and wordpress_get_product_seo (for products).

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 lacks explicit guidance on when to use this tool versus alternatives. It mentions a prerequisite (SEO API Bridge plugin) but does not provide context about when it is appropriate to use this tool or when not to. No mention of alternatives or typical use cases.

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