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

Annotations mark this read-only, and the description adds useful beyond-annotation context: public channels need no authentication, restricted channels need a bearer, and messages are returned newest first. However, the pagination note calls `before` the 'oldest msgid,' which conflicts with the schema's explicit 'timestamp field, not the msgid,' slightly reducing reliability.

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 tight sentences, front-loaded with the core action and then adding only essential extras: ordering, pagination, and authentication. The pagination sentence contains a factual error, but the structure itself is efficient and appropriately sized.

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?

With an output schema and annotations present, the description does not need to explain return values, and it does cover ordering and auth requirements. The `before`/msgid error leaves the pagination guidance incomplete, and there is no sibling routing, so an agent must rely on the schema to avoid misusing the parameter.

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%, so the baseline is 3, but the description's `before` guidance is actively misleading: it says to pass the oldest msgid, while the schema says `before` is a Unix-seconds timestamp and expressly 'not the msgid.' This misinformation lowers the score.

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 opens with a clear verb and resource: 'Read recent messages from a channel' and adds 'newest first,' which matches the title. It does not explicitly contrast with siblings like freeq_search or freeq_pins, so differentiation is left mostly 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 no guidance about when to choose this tool over siblings such as freeq_search or freeq_pins. It discusses pagination mechanics ('Page backwards by passing...') but does not provide when-to-use or when-not-to-use context for tool selection.

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