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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds genuinely new facts: an access restriction (participants only) and deterministic ascending ordering of results. It does not discuss truncation or thread size limits, which is the remaining gap.

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 the operation and ordering front-loaded and the follow-up action last. No filler and nothing repeated from the schema.

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 single-param, non-destructive read with no output schema, the definition covers access, ordering, and the reply path, which is most of what an agent needs. It leaves the shape of the returned thread implicit, an acceptable but real gap.

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% and the schema already says the id can be any message in the thread. The description's "whole thread" framing is consistent with that but adds no syntax or format detail beyond the schema, so the 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?

"Read a whole thread, oldest first" gives a specific verb (read), resource (thread), and ordering guarantee, which distinguishes it from a single-message read. It stops short of naming how it differs from kb_read or kb_search, so an agent must infer the boundary.

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?

It states an eligibility condition (only participants can read) and routes the follow-up action to kb_send with a thread argument. That is clear context, but there is no explicit statement of when to prefer this over kb_read or kb_search on the same content.

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