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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds behavioral details beyond those: ordered reading, pagination via after_seq, the 'not found' response for a wrong token, and that calls count toward an hourly read cap. This is substantial additional transparency 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 three short sentences, front-loaded with the core action, followed by scoping and constraint details. Every sentence carries essential information with no filler or repetition.

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 tool with comprehensive annotations and a fully described schema, the description covers the key operational aspects: ordering, pagination, token handling, and rate limits. It doesn't explicitly state what 'entries' are or the response shape, but no output schema exists and the tool name plus siblings make this reasonably inferable, leaving only minor gaps.

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 100% schema description coverage, the schema already documents all five parameters. The description adds value by clarifying pagination semantics (after_seq for ordered pagination) and token-room behavior (wrong token returns 'not found'), which enriches the otherwise basic schema descriptions.

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 states a specific action and resource: 'Read entries in order', which is distinct from siblings like continental_room_write or continental_room_burn. It also adds meaningful scoping details (pagination, token rooms) that make the tool's role immediately clear.

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 useful context: after_seq for pagination, room_token requirement for token rooms, and a rate limit note. However, it does not explicitly contrast this tool with alternatives like continental_read_messages or continental_inbox, nor state when not to use it, so the guidance is implied rather than explicit.

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