wp_list_posts

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

No annotations are provided, so the description carries full burden. It mentions 'enhanced metadata display' but does not detail behavioral aspects like mutability, rate limits, or pagination limits (max 100 per page only in schema). The inclusion of a non-existent `--page` parameter in examples is misleading.

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 initially concise with a one-sentence purpose and example list. However, the phrase 'enhanced metadata display' is vague. The incorrect `--page` example wastes space and could confuse. Front-loading is adequate but accuracy suffers.

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 6 optional parameters and no output schema, the description covers filtering options and shows examples. But it omits explanation of the `site` parameter (required for multi-site) and does not describe return format. It is minimally adequate but has gaps.

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 100%, so baseline is 3. The description adds usage examples illustrating parameter combinations, adding value beyond schema. However, the example with `--page` (not in schema) detracts from clarity. Overall, helpful but with a notable error.

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 explicitly states 'Lists posts from a WordPress site', using a specific verb and resource. It distinguishes from sibling tools like wp_list_pages and wp_list_categories by clearly targeting posts. The examples reinforce 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?

The description clearly implies when to use this tool (to list posts with filtering), but does not explicitly exclude alternatives or state prerequisites. The context is clear for distinguishing from siblings, but lacks explicit 'when not to use' guidance.

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