wordpress_get_page

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

With no annotations, the description carries the transparency burden. It states the tool 'Get's' a page, which indicates a read-only, side-effect-free operation, and mentions returning full content. However, it does not disclose authentication requirements, error handling for missing/private pages, or any other behavioral caveats.

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 compact and front-loaded with the main purpose. The Args/Returns sections are minimal and every sentence adds useful information. No fluff or unnecessary detail.

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-ID getter, the description covers the main action and return value, and an output schema exists. However, it lacks guidance on when to use this versus sibling tools (e.g., wordpress_get_post), and does not mention error or permission behavior. These gaps are notable given the rich sibling context.

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 provides the parameter name and type; the description adds 'Page ID' as a semantic label, which is helpful but mostly redundant with the parameter name. It does not explain how to obtain the ID or any special constraints, so the added value is minimal but non-zero.

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 uses a specific verb ('Get') and resource ('single WordPress page by ID'), clearly distinguishing from list operations and from wordpress_get_post by specifying 'page'. It also notes 'full content', which clarifies what is retrieved.

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 this is for retrieving a specific page when the ID is known, but it does not explicitly state when to use this over siblings like wordpress_list_pages or wordpress_get_post. No alternatives or exclusion criteria are provided.

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