wordpress_get_pages

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

With no annotations, the description must fully disclose behavior. It only states that pages are retrieved with hierarchy and ordering, but does not explain pagination, whether it is read-only, authentication requirements, or any side effects. Critical behavioral traits like pagination (implied by parameters perPage and page) are not described.

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 concise sentence, which is efficient but perhaps too terse. Every word earns its place, but it omits important details that would make it more useful, striking a balance between brevity and completeness.

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 complexity (pagination, hierarchy) and the absence of output schema and annotations, the description is incomplete. It does not describe return values, pagination behavior, or how hierarchy/ordering work, leaving significant gaps for an AI agent trying to use this tool effectively.

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 0%, meaning the parameters perPage and page have no descriptions in the schema. The description does not add any meaning to these parameters, failing to explain that they control pagination. The agent has no insight into what values to provide.

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 states 'Get pages with hierarchy and ordering', clearly identifying the verb (Get) and resource (pages), and hints at unique features (hierarchy, ordering). However, it does not explicitly differentiate from sibling tools like wordpress_get_posts or wordpress_get_post, which could lead to confusion.

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 such as wordpress_get_posts or wordpress_get_page. There is no mention of prerequisites, conditions, or exclusions, leaving the agent without context for proper selection.

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