wp_get_page

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

With no annotations, the description carries the full burden, and 'Get' clearly signals a read-only retrieval rather than a mutation. It does not disclose behavior such as what happens when the ID does not exist, authentication requirements, or the response shape, but for a simple getter the basic behavior is reasonably transparent.

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, front-loaded sentence with no filler or redundant phrasing. Every word earns its place, and it is appropriately sized for a tool with one parameter.

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 tool is simple: one required parameter, no output schema, and no annotations. The description tells the agent what the tool does and which parameter matters, which is sufficient for basic invocation. However, it does not mention return contents, error behavior, or any prerequisites, leaving a few gaps for a fully self-contained definition.

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?

The input schema only defines 'id' as an integer with no description, and schema description coverage is 0%. The description adds minimal meaning by clarifying the parameter is the page ID, but it does not explain that this is the WordPress page identifier or how it relates to the returned resource beyond the obvious reading.

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 a specific verb ('Get'), a specific resource ('WordPress page'), and the access pattern ('by ID'). It clearly distinguishes from sibling tools like wp_list_pages (listing) and wp_get_post (a different content type).

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 phrase 'single ... by ID' implies when to use this tool: when the agent needs exactly one page and already has its ID. However, it does not explicitly mention alternatives or exclusion criteria, such as using wp_list_pages for multiple pages or wp_get_post for posts.

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