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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds two things beyond that: an auth precondition (organization API key) and the 'chain check' behavior, which signals the transcript is integrity-verified. That extra context is meaningful, though 'chain check' is not explained.

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 the scope front-loaded and no filler. The 'with the chain check' clause is a touch cryptic, but the definition is tight overall.

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 read-only transcript tool with annotations covering safety and no output schema, the definition covers scope and auth adequately. It omits pagination/limit behavior and any hint about result size, which matters for a message-history endpoint, so it is viable but not complete.

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% with a single room_id parameter whose description ('rm_... ID') already carries the format. The description's phrase 'a room you are part of' loosely mirrors that constraint but adds no syntax or scoping detail beyond the schema, 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 names the resource clearly ('every message in a room you are part of'), so an agent knows this returns a room's message history. However, the verb is implicit and it never distinguishes itself from siblings like room_info or room_verify, which also touch a room.

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?

'Requires the organization API key' gives a real precondition for invocation, which is genuinely useful. But there is no guidance on when to choose this over room_info/room_verify, and no exclusions or alternatives are named.

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