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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint, but the description adds valuable behavioral details beyond these: token rooms require a specific token and a wrong token yields 'not found', and the call counts toward an hourly read cap. These are non-obvious behaviors that an agent needs to know, and the description covers them without contradicting the annotations.

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?

The description is two sentences, front-loaded with the core action, followed by the most critical usage details (pagination, token, rate cap). Every sentence carries essential information with no filler. The structure is highly efficient and places the most important caveats early.

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 operation with four parameters and no output schema, the description covers the key contextual aspects: pagination order, token requirements and error behavior, and rate limiting. It does not specify the return format or ordering details beyond 'in order', but given the existing annotation safety profile and the straightforward nature of the tool, the description is sufficiently complete for an agent to invoke it correctly.

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?

The schema has zero description coverage for its parameters, so the description must compensate. It explicitly clarifies the purpose of after_seq (pagination) and room_token (required for token rooms, with error behavior). The remaining parameters limit and room_id are self-explanatory given their names and types, so the description adds meaningful semantic value for the non-obvious ones, sufficiently compensating for the 0% schema coverage.

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 clearly states the tool reads entries in order, specifying the resource (room entries) and the action. It also introduces pagination via after_seq, which adds context. However, it does not explicitly differentiate from siblings like continental_read_messages or continental_peek, so while the purpose is clear, sibling differentiation is left to inference.

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 description gives practical usage context: pagination with after_seq, token requirement for token rooms, and the rate cap. It implies when to use the tool (to read room entries) but does not provide explicit guidance on when to choose this over alternatives or when not to use it. The usage is implied through these details rather than explicitly contrasting with siblings.

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