wp_list_posts

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only says 'list with optional filters' and does not reveal key behaviors like pagination, sorting, or output format. The schema hints at pagination via per_page and page, but the description adds no extra behavioral context.

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 concise sentence with no unnecessary words. While efficiently front-loaded, it could benefit from slight expansion to cover key behaviors without becoming verbose.

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 the absence of an output schema and the tool's moderate complexity (9 parameters), the description is incomplete. It does not describe the return format, default behavior, or how to handle edge cases, leaving the agent with insufficient guidance for correct invocation.

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 high (78%), so baseline is 3. However, the description adds no meaning beyond the schema; it merely reiterates 'optional filters'. It does not explain how filters combine or provide usage examples, falling short of adding value.

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 the action 'List' and the resource 'WordPress posts' with optional filters. However, it does not distinguish from sibling tools like wp_list_pages or wp_search_posts, and it does not clarify whether 'posts' includes custom post types, which could be ambiguous.

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 tool versus siblings such as wp_search_posts or mcp_list_cpt_posts. The description lacks context on when to choose this specific listing function over others.

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