wp_get_post

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

There are no annotations, so the description carries the full burden. 'Get' signals a read-like operation, but the description does not clarify return behavior, whether the post is returned in a particular status, error cases, or whether this is safe and idempotent. It adds little beyond the tool's name.

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, direct sentence. Every word is meaningful, and there is no filler or redundancy.

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 one-parameter getter with no output schema, the description is minimally usable: an agent knows to supply a post ID. But with no annotations and no output schema, the lack of return shape and behavioral detail leaves meaningful gaps.

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 schema documents id as a required integer with bounds but provides no description. The description supplies the key semantic: the id identifies the WordPress post to retrieve. This is helpful but minimal, and it does not add other parameter details.

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 names a specific verb ('Get'), a specific resource ('a single WordPress post'), and a precise selector ('by ID'). This clearly distinguishes it from siblings like wp_list_posts, wp_get_page, and the post mutation tools.

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 wording implies when to use the tool: when you know a specific post ID and need one post. However, it gives no explicit guidance about when not to use it or which sibling to prefer, so the routing is left implicit.

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