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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description mostly restates that with "read-only, runs straight away." It does add nothing new about what is returned or any auth/site scoping constraints, so it neither contradicts nor enriches the annotation profile.

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?

A single short sentence with the key operation front-loaded and no filler. The parenthetical site note and the "Through Royally" clause are slightly noisy but not wasteful enough to penalize further.

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 simple read with full schema coverage and rich annotations, no return-value explanation is needed. However, given a sibling set containing wp_get_pages, wp_get_post and competing page-getters, the description omits the routing information an agent needs to pick correctly.

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 coverage is 100% — both id and the site_id enum are documented in the schema — so the schema carries the semantic load. The description's "by ID" merely echoes the required parameter rather than adding format or constraint detail, which is baseline 3.

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 ("Get single page by ID") and implicitly contrasts with the plural sibling wp_get_pages. It does not mention when to prefer it over wp_get_post or the mcp-easy-ai variant, so it stops short of full differentiation.

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 versus wp_get_pages, wp_get_post, or the many other page-reading siblings. The only usage-like clause, "runs straight away," describes execution timing, not selection criteria.

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