wp_list_pages

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate that. It adds value by specifying the return fields (page ID, title, status, parent page) and the browsing purpose, which is contextual behavior beyond the annotations. No contradictions with annotations are present.

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 two concise sentences. The first sentence states the primary action, and the second adds return fields and a use case. Every word earns its place; there is no redundancy or filler.

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?

The tool is simple (two optional parameters, no output schema). The description covers the core purpose, return fields, and typical use. It does not explicitly mention pagination or default limits, but those are documented in the schema. Given the richness of the schema and annotations, the description is adequately complete for this tool.

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 input schema provides 100% coverage for both parameters (status and per_page) with clear descriptions. The tool description itself does not explain any parameter semantics, but because the schema already handles this, the baseline of 3 is appropriate.

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 opens with 'List WordPress pages', a specific verb and resource that clearly indicates the tool returns multiple pages. It further details the returned fields (page ID, title, status, parent page) and distinguishes it from siblings like wp_get_page (which retrieves a single page) and wp_list_posts (which lists posts, not pages). The phrase 'browse site page structure' reinforces its 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 provides a clear use case: 'Use to browse site page structure.' This implies when to use this tool versus fetching a specific page or listing posts. However, it does not explicitly state when not to use it or name alternative tools, so it lacks the explicit exclusion or alternative guidance seen in higher-scoring examples.

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