MCP Hub

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

No annotations provided, so description carries full burden. Discloses mutation nature and external plugin dependency, but lacks detail on error behavior, partial update handling (all 11 SEO fields are optional), or idempotency guarantees expected for a 13-parameter mutation 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?

Three efficient sentences with purpose front-loaded. The '[UNIFIED]' prefix is slightly noisy metadata, but overall structure is tight with no redundant content.

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?

Adequate for basic tool selection given complexity, but insufficient for invocation readiness. With 13 parameters at 0% schema coverage and no output schema, the description should explain parameter relationships or return structure; currently leaves significant documentation gaps.

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 has 0% description coverage across 13 parameters, yet description adds no parameter semantics beyond implicitly acknowledging 'product_id' via 'WooCommerce product'. Critical gap: 'site' parameter format, SEO field purposes, and optional vs required distinctions (only 2 required) are undocumented in both schema and description.

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: states exact action ('Update SEO metadata'), target resource ('WooCommerce product'), and explicitly differentiates from sibling tool ('Same as update_post_seo but specifically for products'), making selection 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?

Provides clear prerequisite ('Requires SEO API Bridge plugin') and implies vs alternatives by contrasting with update_post_seo. Could be slightly more explicit with a 'Use update_post_seo for posts' directive, but sufficiently guides selection.

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