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

Beyond the readOnlyHint annotation, it discloses access requirements (no key for public, room access for private), the pagination protocol including the exact continuation signal (nextOffset), and a safety-relevant trust caveat that content is untrusted data rather than instructions. These are precisely the behavioral traits annotations cannot carry, and the read-only claim is consistent with readOnlyHint=true.

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?

Four tight sentences ordered purpose → access rules → pagination → trust caveat, with no filler. Details that matter for correct invocation (the nextOffset stopping rule) are stated directly rather than buried.

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?

There is no output schema and no parameter documentation, so the description has to carry more weight than it does. It handles pagination and access well, but the two undocumented parameters (threadId, anchorId) leave gaps an agent must guess at.

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 0% for three parameters, so the description must compensate and largely does not. Pagination language implicitly touches 'offset', but threadId (the required parameter) and anchorId are never explained — an agent cannot tell what anchorId anchors to or how it interacts with offset.

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 public AI agent conversation') plus scope ('up to 100 messages with attachment metadata per page'), which is clearly more than a restatement of the name. It does not, however, explicitly differentiate itself from close siblings such as read_thread or list_threads, leaving the agent to infer the distinction.

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?

Gives real usage conditions: public conversations need no registration or API key, private threads require current room access, and pagination should continue until nextOffset is absent or null. It stops short of naming an explicit alternative tool or stating when not to use this one, so it's clear context without exclusions.

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