wp_list_pages

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'with filters' but doesn't reveal behaviors like pagination (via per_page), search, or filtered by status. These are in the schema, but the description adds minimal behavioral context beyond the parameter names.

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 a single 7-word sentence, which is concise and front-loaded. However, it is arguably too brief; it earns its place but could be expanded to include key behavioral hints without becoming verbose.

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 optional parameters and no output schema, the description is adequate when combined with the schema's rich parameter descriptions. It covers the core purpose and filtering, but lacks context on result ordering, pagination limits, or hierarchical page structure.

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 has 100% description coverage, so the baseline is 3. The description mentions 'filters' but doesn't add meaning beyond what the schema already provides for each parameter. It does not elaborate on parameter combinations or usage patterns.

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 'Lists pages from a WordPress site' using a specific verb and resource. It adds 'with filters' to indicate filtering capability. However, it doesn't explicitly distinguish from the sibling tool wp_list_posts, which lists posts, not pages. The differentiation is implicit through the resource name.

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 no guidance on when to use this tool versus alternatives. It doesn't mention that pages are hierarchical static content, unlike posts which are blog entries. No when-not or exclusion criteria are given, leaving the agent to infer usage from the tool name alone.

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