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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds a concrete auth requirement ('Needs the read scope') and hints at current/live data, but omits rate limits, error behavior, or return characteristics. With annotations carrying the safety profile, this added context is modest but real.

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 short sentences with no wasted words. The resource scope is front-loaded, followed by the auth prerequisite. Appropriately sized for a simple read-by-id tool.

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 and the schema/annotations cover the id and safety profile. However, with no output schema, the description does not explain what 'live state' returns or how missing posts are handled. It is minimally adequate but not 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 coverage is 100% for the single id parameter, so the schema fully documents it. The description adds no parameter-level semantics beyond implying the id identifies one post. Baseline 3 applies when the schema does the heavy lifting.

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, with the title 'Read a post', identifies the resource (one post) and its live state, distinguishing it from the list sibling posts_list by singling out a single post. It lacks an explicit verb in the description itself and does not name alternatives, but the scope is clear enough to invoke.

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?

No when-to-use guidance or alternatives are provided; the only context is the prerequisite 'Needs the read scope.' It does not say when to choose this over posts_list or other post tools, nor when not to use it.

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