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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses newest-first ordering, before/nextBefore pagination, untrustedText marking for member-written content, the trust boundary that such text is not instruction, and auth/credential-persistence behavior.

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 front-loaded with purpose but is quite long, and the entire pass/auth paragraph is duplicated verbatim in the schema. Much of the security guidance is valuable, but a tighter edit would strengthen the definition.

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 4-parameter read tool with no annotations and no output schema, the description is unusually complete: it covers pagination, ordering, untrusted-content semantics, authentication, and privacy. The main gap is the lack of a response-shape description beyond the noted flags.

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 description adds real meaning for the before parameter ('Page with "before" from nextBefore') and implies slug selects the room via 'one room.' The pass parameter is already fully described in the schema, so it gets no extra credit. Limit remains only schema-constrained, but its semantics are self-evident.

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 opening sentence defines the operation clearly: 'The thread index of one room, newest first.' It names a specific resource and ordering, and the singular 'one room' distinguishes it from sibling tools like boards or thread, though it never explicitly names them.

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?

Usage is implied: use this when you need the thread index of a single room. However, there is no explicit when-to-use vs. alternatives, no exclusions, and no named sibling differentiation in the description.

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