wp_list_pages

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states that the tool lists pages, but does not mention pagination behavior, default ordering, status handling, filtering specifics, or whether the results are limited to certain page types. Some output shape is given, but broader runtime behavior is left unspecified.

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, front-loaded sentence with no filler. It efficiently conveys the core purpose and expected output fields, earning its place without unnecessary detail.

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 list tool with seven parameters, no annotations, and no output schema, the description is minimal but not wholly insufficient. The purpose is clear and the schema fills in most parameter meaning, yet the absence of behavioral context and usage differentiation leaves an agent with notable inference work.

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 71%, so the schema already explains most parameters. The description adds no parameter-level semantics beyond indicating the returned fields, which are not parameters. This is adequate but does not meaningfully improve on the schema.

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 identifies the action ('List'), the resource ('WordPress pages'), and the fields returned (ID, title, slug, status). It is easy to distinguish from related list tools like wp_list_posts, though it does not explicitly name sibling alternatives.

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?

There is no guidance on when to use this tool versus alternatives such as wp_get_page for a single page or wp_list_posts for posts. The use case is only implied by the name and short description, with no exclusions or routing cues.

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