Get one post / page

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

With no annotations provided, the description carries the burden of behavioral disclosure. It indicates the tool fetches raw content, adding value beyond the schema, but it does not explicitly state that the operation is read-only, nor does it mention error behavior or edge cases. This is adequate but lacks full safety/behavior clarity.

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 that communicates the core purpose, content detail, and usage intent without any wasted words. Every part contributes meaningful information.

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-only tool with three parameters and no output schema, the description provides sufficient context: it states what is returned (full raw content) and when to use it. Minor gaps like lack of explicit read-only confirmation and error handling are present, but given the low complexity, the description is nearly complete.

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 all parameters (id, site, post_type) are already documented with descriptions. The main description adds context about the returned content ('full, including raw block/HTML') but does not provide any additional parameter-level semantics, meriting the 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?

The description 'Fetch a single item in full, including its raw block/HTML content' uses a specific verb and resource, clearly distinguishing it from list/search tools. The phrase 'this is what you read before editing something' further reinforces its purpose as a content retrieval tool for editing workflows.

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 provides clear context for when to use this tool ('before editing something'), implying it is the preferred way to fetch full content. However, it does not explicitly mention when not to use it or name alternatives like wp_list_content or wp_search, so it stops short of full exclusionary guidance.

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