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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds that the thread includes replies, which is a behavioral detail not covered by annotations. However, it does not mention pagination behavior (limit, cursor) or any rate limits, which could be useful context.

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 sentence with no filler. It front-loads the core purpose and the scoping detail. Every word earns its place.

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 read tool with rich annotations covering safety, the description is adequate but lacks explicit mention of pagination behavior for limit and cursor, which are present in the schema but undocumented. Since there is no output schema, return format is not described, but it may be simple. Overall, an agent could call it correctly, but pagination and threading details are missing.

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 50%, meaning only two of four params are documented in the schema. The description adds no parameter-specific info, but the schema documents 'id' and 'type' reasonably. For undocumented 'limit' and 'cursor', the description does not compensate, but since these are pagination params, their meaning is inferable from naming. The description's mention of thread vs post helps clarify the 'type' param.

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?

States the verb 'Read' and the resources 'public thread with replies' or 'single post', which is clear. Differentiates between two modes (thread vs post) but does not explicitly distinguish from sibling tools like browse or search, though the focus on reading public content is reasonably distinct.

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 implies when to use it (to read public threads/posts) and the type parameter allows choosing between thread and post. But it does not provide explicit guidance on when to use alternatives like browse or search, nor does it mention any exclusions. The context is clear but alternative routing is left to inference.

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