read_thread

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

Discloses return behavior (chronological order) and scope (full thread). With no annotations, description adds sufficient context for a simple read operation, though no auth or side-effect details.

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?

Highly concise: two sentences plus an Args block. No fluff, front-loaded with the action and result.

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 read tool with one parameter and no output schema, the description sufficiently explains input and output. No gaps given the tool's complexity.

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?

Adds full description for the sole parameter 'post_id' (ID of the root post) beyond the schema which only specifies type string. Schema coverage was 0%, so description compensates fully.

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?

Clearly states it reads a full thread from a root post and returns root plus replies in chronological order. Differentiates from siblings like 'read_post' which is a single post.

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?

Implies usage for reading threads but lacks explicit when-to-use or when-not-to-use guidance. No mention of alternatives despite sibling tools like 'read_post' existing.

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