MCP Hub

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

With no annotations provided, the description carries full burden. It discloses pagination behavior and return fields (author, content, moderation status), but lacks safety profile confirmation (read-only implied but not stated), auth requirements, or error conditions.

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?

Two efficient sentences with information front-loaded. The '[UNIFIED]' prefix is structural noise that doesn't aid selection, but overall minimal waste.

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 zero schema descriptions and no output schema, the description partially compensates by describing return structure (author, content, status). However, with 5 undocumented parameters including 1 required, it falls short of fully contextualizing the tool's interface.

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. The description fails to compensate by documenting the required 'site' parameter (format unclear) or explaining 'status' values ('approve' default mentioned only in schema). Only marginally references pagination via 'paginated list' mention.

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 uses specific verb 'List' with resource 'WordPress comments' and distinguishes from sibling 'wordpress_get_comment' by explicitly stating it returns a 'paginated list' (plural/multiple) versus a single item.

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?

No guidance on when to use this versus 'wordpress_get_comment' for single comment retrieval, or when to filter by post_id versus retrieving all comments. No mention of pagination handling patterns.

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