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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that it returns 'full content', which is a useful behavioral detail distinguishing it from excerpt-level fetches, but says nothing about auth needs or pagination.

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 front-loaded sentence that covers verb, resource, and scope with no wasted words. Appropriately sized for a simple retrieval tool.

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 single-resource read whose annotations already carry the safety profile and whose parameters are fully documented, the description is nearly sufficient. The only gap is the lack of differentiation from similar get_* siblings, which is minor for this complexity level.

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 both id and site_id are already documented in the schema. The description reinforces that retrieval is 'by ID' but adds no format or range detail beyond what structured data provides, making the baseline 3 appropriate.

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 (Get), resource (WordPress page), and scope (single, by ID, full content). It implicitly separates pages from posts via the resource noun, though it doesn't explicitly distinguish itself from close siblings like wp_get_page_html or wp_get_post.

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?

No when-to-use guidance or alternatives are offered. An agent gets no signal about when to prefer this over wp_get_page_html or wp_get_post, nor any prerequisite conditions such as needing a connected site.

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