wp_list_pages

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

The description mentions 'Read-only' indicating no side effects, but since no annotations are provided, the description should disclose more behavioral traits such as return format, pagination limits, or any authentication requirements. It lacks sufficient detail.

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 concise and front-loaded, consisting of two clear sentences with no redundant information. Every word adds value.

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 tool has 4 parameters and no output schema or annotations, the description is somewhat incomplete. It covers the main features but omits details like default pagination, error handling, and return format. For a simple list tool, it is minimally adequate.

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 adds meaning to the parameters by mentioning 'pagination' (for page and per_page), 'status filter' (for status), and 'search' (for search). However, it does not enumerate allowed values or format expectations for any parameter, and with 0% schema description coverage, more detail would be beneficial.

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 verb 'List' and the resource 'WordPress pages'. It also mentions supported features (pagination, status filter, search) which distinguishes it from sibling tools like wp_list_posts and wp_get_page.

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 this tool is for listing pages with filtering options and is read-only, but it does not provide explicit guidance on when to use it versus alternatives like wp_get_page or wp_search_content. No when-not-to-use conditions are stated.

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