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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so "read-only, runs straight away" largely restates structured data. The genuinely additive part is the disclosure of the response shape and that content_length is bytes of *stored* content, but pagination behavior (per_page default/max, whether a total is returned) is left unstated.

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?

Three short sentences, front-loaded with purpose then return shape then filtering, with no filler. The trailing "Through Royally: read-only, runs straight away" is somewhat redundant with annotations but takes only a clause.

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?

With no output schema, the description usefully enumerates the return fields and explains content_length, which is the main ambiguity an agent would face. The remaining gap is pagination/total-count behaviour, which matters for a list tool with a max of 100.

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 are already documented, including the enum values for status and site_id. The description only reinforces the parent-filtering crawl pattern and adds nothing about status semantics or pagination, so baseline 3 applies.

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?

States a specific verb and resource ("List WordPress pages") and enumerates the returned fields, so the agent knows exactly what it gets. It doesn't explicitly contrast itself with the many nearby siblings (wp_get_posts, wp_list_pages, wp_get_page), which keeps it just short of a 5.

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?

"Filter by parent to walk the page hierarchy" and "size-check before fetching" give concrete usage contexts, the latter implicitly routing the agent to fetch full content only for small pages. It stops short of naming the alternative tool (e.g. wp_get_page) for that fetch step, so there is no explicit when-not.

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