wordpress_get_product_seo

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

With no annotations, the description must fully disclose behavioral traits. It states the tool returns SEO metadata and requires a plugin, but does not mention side effects (none expected for read), authentication requirements, rate limits, or what happens if the plugin is missing. The description is adequate but not highly transparent.

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 (one sentence plus a requirement) and front-loads the purpose. The '[UNIFIED]' prefix adds minimal value but does not detract. It could be slightly more structured, but remains efficient.

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 lack of output schema, parameter descriptions, and annotations, the description provides only the basic purpose and a requirement. It misses details about parameter semantics, error conditions, and return structure, leaving notable gaps for an agent to use the tool correctly.

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%, and the description does not explain the 'site' and 'product_id' parameters beyond the tool's general purpose. Without explicit parameter details, an agent cannot infer valid values or formats, which is a significant gap.

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 retrieves SEO metadata for a WooCommerce product, specifies the supported plugins (Rank Math or Yoast) and required fields, and implicitly distinguishes from sibling tools like wordpress_get_post_seo (for posts) and wordpress_update_product_seo (for updates).

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 provides a prerequisite ('Requires SEO API Bridge plugin') but does not explicitly state when to use this tool versus alternatives like wordpress_update_product_seo or wordpress_get_post_seo. The usage context is implied by the tool's name and purpose, but lacks explicit guidance.

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