wp_get_page

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

With no annotations, the description partially covers transparency by stating it 'Retrieves' (implying read-only) and mentions the optional 'full content' parameter. However, it does not explicitly confirm no side effects or disclose any other behavioral traits.

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, well-structured sentence with no superfluous words. It efficiently conveys the core action, resource, and key parameter behavior.

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?

The description adequately covers the core function and key parameter. Without an output schema, it does not describe the return format, which could be helpful but is not critical given the tool's simplicity and common expectation of returning a page object.

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 covers all parameters (100%). The description adds minor context ('for editing') to the include_content parameter, but does not meaningfully extend understanding of site or id parameters. Baseline 3 applies with marginal enhancement.

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 states the verb 'Retrieves' and the resource 'a single page by its ID', which precisely defines the function. It implicitly distinguishes from sibling tools like wp_list_pages (list) and wp_get_post (post) by specifying 'page'.

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 implies usage when needing a single page by ID but does not explicitly contrast with alternatives like wp_get_post for posts or wp_list_pages for multiple pages. No when-not-to-use guidance is provided.

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