Read a thread

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

Annotations already cover readOnly, idempotent, non-destructive, and open-world traits, so the safety profile is handled. The description adds genuinely useful behavior beyond that: results are decrypted and returned in chronological order as a complete thread, which tells the agent what it will actually receive.

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 sentences, zero fat, with the core operation front-loaded. The closing sentence is softer motivation rather than instruction, which slightly dilutes conciseness but still earns its place as retrieval context.

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?

With no output schema, the description responsibly characterizes the return shape (root plus chronological replies). Annotations cover safety, and parameters are fully documented, so the only minor omission is pagination/limit behavior for large threads.

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 100%, so the schema already documents url, limit, and thread_id. The description restates that the input may be a root id, any reply id, or a pasted URL, adding slight clarity but no format or default details beyond the schema; baseline 3 applies.

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 a specific verb and resource ('Read a whole thread'), plus the exact scope returned (root message plus all replies, chronological, decrypted). An agent can distinguish this from get_message (single message) and search without ambiguity.

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 trailing sentence ('Threads are where most how-tos and decisions are discussed') gives motivational context for why a thread read matters, but there is no explicit when-to-use vs when-not guidance and no named alternatives such as get_message. Usage is implied rather than stated.

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