List WordPress pages

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

No annotations are provided, so the description carries the behavioral burden. It does disclose that this is a GET request, implying a read-only operation, and indicates supported filtering capabilities. But it does not mention authentication needs, default response shape, or WordPress-specific status behavior beyond what the schema already states.

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, information-dense sentences with no filler. The endpoint is included, the primary action is front-loaded, and the supported capabilities are listed clearly without redundancy.

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 read-only list tool with fully documented optional parameters and no output schema, the description plus schema covers endpoint, action, and filters. It could be more complete by noting that get_page should be used for a single page or describing the expected response collection, but these are minor 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 description coverage is 100%, so all four parameters already have meaningful descriptions. The tool description only groups them at a high level ('search, pagination and status filtering') and does not add details beyond what the schema provides, which warrants the baseline score.

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 uses a specific verb ('List/search') and a clear resource ('pages on the connected WordPress site'), and adds the exact endpoint. It is clear enough to be distinguished from get_page/create_page/update_page by collection-vs-singular and read-vs-write semantics, though it does not explicitly name a sibling alternative.

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 intended usage is implied by 'List/search pages' and the mention of search, pagination, and status filtering. However, the description does not explicitly say when to prefer this over get_page for a single page, or when not to use it, so the guidance is only implicit.

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