wp_list_posts

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

With no annotations provided, the description carries the full burden of disclosing behavior, but it only mentions returned fields. It does not disclose pagination behavior, default per_page limit of 20, read-only nature, ordering defaults, or any side effects. This is a significant gap for a list operation with multiple filters.

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 a single efficient sentence with no wasted words. It front-loads the action and resource, and every word contributes to the core meaning.

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 9 optional parameters, no annotations, and no output schema, this description is incomplete. It does not mention filtering by status, tags, categories, author, or search, nor does it explain pagination or the shape of the response beyond four fields. An agent would not know how to perform common filtered listing tasks without opening the schema.

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 description coverage is 78%, which is near the high baseline, and the description adds no parameter-level meaning. The parameters are mostly documented in the schema, so the description does not need to repeat them, but it also does not clarify ambiguous ones like orderby or how filters combine.

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 states a specific verb ('List'), resource ('WordPress posts'), and the key return fields (ID, title, slug, status). It clearly distinguishes this from sibling list tools like wp_list_pages and wp_list_media by naming posts explicitly.

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 gives no guidance on when to use this tool versus alternatives such as wp_get_post for a single post or wp_list_pages for pages. There is no mention of exclusions, prerequisites, or conditions that would route an agent to a sibling tool.

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