Read Post

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read. The description adds useful behavioral context by specifying that the result includes raw markdown and metadata, going beyond a generic 'read post' statement. No contradictory behavior is described.

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 sentence with no filler. It front-loads the action and resource, then specifies the input and output. Every word contributes to understanding the tool's purpose.

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 read-only tool with no output schema, the description is sufficient: it names the input, the scope, and the return content. The annotations cover the safety profile, and the simplicity of the tool means no additional explanation is necessary.

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 already describes post_id as 'the post id' with 100% coverage, so the description's 'by post id' adds no additional semantic detail. This is an adequate baseline for a fully schema-documented single 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 a specific verb ('Read'), a specific resource ('a single post'), the input key ('by post id'), and the output type ('raw markdown and metadata'). This distinguishes it from sibling tools like discourse_read_topic or discourse_search by focusing on a single post and its raw content.

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 phrase 'by post id' gives clear context for when to use this tool: when the agent already has a post_id and needs that specific post's content. It does not explicitly name alternatives or exclusions, but the intended use case is unambiguous given the sibling tool names.

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