wp_posts_list

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

The description goes beyond the schema by stating that it returns 'normalized post summaries' and listing the included fields, which signals that this is not a full-content endpoint. However, with no annotations, it omits behavioral details such as pagination, default status/order, or edge cases, leaving some transparency gaps.

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 two sentences, front-loaded with purpose and filters, and wastes no words. Every sentence carries useful information, including return type and the pointer to wp_posts_get.

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?

For a tool with 11 parameters and no output schema, the description covers the core purpose, filters, and return fields, but omits pagination behavior, defaults, and full parameter explanations. It is adequate for a basic understanding but incomplete for a fully autonomous agent.

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?

The description groups parameters into filter categories (status, search, author, categories, tags, date range, ordering), giving high-level meaning that the schema lacks. It fails to mention pagination parameters (page, per_page) and doesn't explain formats or how filters combine, so it provides only partial value beyond the schema.

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 'List blog posts with filters' and specifies the resource (blog posts) and the action (list). It also distinguishes itself from the sibling tool wp_posts_get by noting 'Use wp_posts_get to fetch full content,' clarifying the scope of this tool as a summary-returning list operation.

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 implies use when you need a filterable list of posts, and explicitly provides a pointer to an alternative: 'Use wp_posts_get to fetch full content.' However, it doesn't explicitly contrast with wp_search_posts or mention exclusions, so it earns a 4 rather than a 5.

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