wp_get_post

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

Annotations already provide readOnlyHint=true and destructiveHint=false, covering safety. The description adds that the tool returns full content, metadata, categories, and tags, which is useful context beyond annotations. No contradiction; not rich enough for a higher score.

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?

Two concise sentences, first directly identifies the action and resource, second adds usage guidance. 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 simple one-parameter read tool, the description fully covers what it does, what it returns, and when to use it. Annotations cover the read-only safety profile, and no output schema is needed due to the return description.

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 covers 100% of parameters with 'id' described as 'Post ID'. The description doesn't add additional parameter meaning, but the baseline of 3 is appropriate given full schema coverage for a trivial parameter.

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 tool 'Get a single WordPress post' with specific return details ('full content, metadata, categories, and tags'). This distinguishes it from sibling tools like wp_list_posts (multiple) and wp_update_post (modification).

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 says 'Use to inspect post content before editing', providing clear context for when to use. However, it does not explicitly exclude alternatives like wp_list_posts or mention when not to use, so it falls short of a 5.

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