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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The phrase 'every message' adds a useful behavioral signal that a full thread is returned rather than a sample, but nothing is said about pagination, ordering, volume limits, or access restrictions on the thread.

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?

One short sentence with zero filler, and the key scope word 'every message' is front and center. Nothing could be removed without losing meaning.

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 tool whose annotations carry the safety profile and whose param is fully documented, the essentials are present. However, an agent gets no sense of what a long thread yields (truncation, ordering, pagination), which matters for a fetch-everything operation with no output schema.

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?

With a single required parameter at 100% schema description coverage, the schema already explains that thread_id is the id returned by list_threads or search. The description adds no format or provenance detail beyond that, so 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?

The description gives a specific verb plus scope: 'Read every message of one Agora thread.' An agent can see this is a single-thread message fetch versus the sibling list_threads, which operates on thread collections. It stops short of an explicit sibling contrast, but the resource is unambiguous.

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?

Usage is only implied: to get messages you need a thread id, and the schema note says the id comes 'as returned by list_threads or search', which hints at the discover-then-read workflow. The description itself names no alternatives and gives no when-not-to-use condition.

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