wordpress_list_posts

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

No annotations provided, so description carries full burden. Mentions 'paginated' and specific return fields (title, excerpt, status, metadata), which helps. However, lacks disclosure of auth requirements, rate limits, max per_page values, or error behavior when site is invalid.

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-sentence structure is efficient, but the '[UNIFIED]' prefix is wasteful metadata that doesn't aid the agent. Otherwise front-loaded with the action and return structure.

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?

Without output schema, mentioning return fields (title, excerpt, status, metadata) adds necessary value. However, for a 7-parameter tool with zero schema descriptions and no annotations, the description should explain pagination mechanics and parameter relationships more thoroughly.

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 coverage is 0%, leaving 7 parameters undocumented. Description mentions 'paginated' which implicitly hints at page/per_page, but provides no semantics for critical parameters like 'site' (URL vs ID?), 'status' (expected values?), or distinction between 'search' vs 'search_terms'. Insufficient compensation for schema gaps.

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?

States specific verb (List) + resource (WordPress posts) clearly. Distinguishes from siblings like wordpress_list_pages or wordpress_list_comments by specifying 'posts'. The '[UNIFIED]' prefix is noise but doesn't obscure the purpose.

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 no guidance on when to use versus alternatives like wordpress_get_post (single retrieval) or wordpress_list_custom_posts. Does not mention that 'search' and 'search_terms' parameters enable filtering, leaving usage context implied rather than explicit.

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