wp_list_posts

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

With no annotations, the description carries the transparency burden. 'List' clearly marks this as a read-only operation, and the second sentence adds that search and pagination are supported. It does not disclose the default status filter or the shape of results, but for a simple list operation the core behavior is stated unambiguously.

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 short sentences with the action first and no redundant elaboration. Every word contributes; the search/pagination note is the only extra detail and it is useful.

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 simple 4-parameter list tool, the description gives the essential selection criteria and capability. There is no output schema, so return-shape details are absent, and the default behavior of `status` is unspecified, making it adequate but not complete.

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 0%, so the description must compensate. It mentions 'search' and 'pagination,' which maps to `search`, `page`, and `per_page`, but it does not explain `status` semantics or the defaults of the pagination parameters. The enum on `status` helps, but the description leaves part of the parameter surface unexplained.

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 action and resource: 'List WordPress posts.' This clearly identifies the tool as a listing operation and distinguishes it from wp_get_post (single post retrieval) and wp_list_pages (pages) by resource type. It does not explicitly name alternatives or exclusions, so it falls just short of a perfect purpose statement.

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?

'Supports search and pagination' implies when this tool is suitable: when the task needs a filtered, pageinated collection of posts rather than a single post. However, the description never says to use wp_get_post for a single post or wp_list_pages for pages, so the guidance remains 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.