MCP Hub

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

No annotations provided, so description carries full burden. Discloses return value structure ('configuration and post type associations') but omits safety profile (is it cached?), pagination behavior, rate limits, or error handling patterns expected for a 'list' operation.

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?

Efficient two-sentence structure front-loaded with the action. '[UNIFIED]' prefix is slightly unconventional but doesn't impede clarity. No redundant information; every element serves a purpose.

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?

Appropriate for a simple read operation with one parameter. Mentions return value to compensate for lack of output schema. However, incomplete due to missing parameter documentation and lack of behavioral details (pagination, caching) that would help the agent handle the response 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 has 0% description coverage for the single required 'site' parameter. Description fails to compensate by not defining what 'site' represents (URL? ID? slug?), its format, or where to obtain valid values. Agent must guess the parameter's semantics.

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?

Clear verb 'List' and resource 'registered taxonomies'. Distinguishes from siblings by specifying scope includes 'built-in (category, post_tag) and custom taxonomies', implying this returns taxonomy definitions/metadata rather than individual terms (which would be handled by wordpress_list_categories, wordpress_list_tags, or wordpress_list_taxonomy_terms).

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?

Implies usage context by stating it 'Returns configuration and post type associations', suggesting use when metadata about taxonomy structure is needed. However, lacks explicit when-to-use guidance versus the sibling term-listing tools or prerequisites like authentication.

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