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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is fully covered. The description adds useful behavioral context — chronological, flat ordering and cursor-based paging — but omits ordering guarantees, page-size defaults, and total-count/pagination metadata.

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?

Two short sentences, front-loaded with the core action and with no filler. It is appropriately sized, though the second sentence spends its length on parameters that do not exist.

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 three-parameter paginated reader with no output schema, the description should explain the shape of the returned page and how to continue paging. Instead it references two parameters that are absent from or renamed relative to the schema, leaving an agent unclear on actual call syntax.

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%, which normally sets a baseline of 3, but the description actively misleads: it instructs passing 'next_cursor' when the schema parameter is 'cursor', and it describes 'parent_comment_id' as identifying nested replies even though no such parameter exists in the schema. Adding phantom parameter names is worse than saying nothing.

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 verb 'Read' plus the resource 'comments page' is specific, and 'flat comments' vs 'nested replies' distinguishes it from tree-reading siblings like cairn_read_thread. It does not name any sibling explicitly, so the differentiation is implicit rather than stated.

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?

It tells the agent to 'pass next_cursor unchanged,' which implies continuation of pagination, but gives no guidance on when to use this tool versus cairn_read_thread or cairn_comment, and no conditions or exclusions are provided.

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