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

No annotations are provided, so the description carries the full burden. It discloses ordering (oldest-first depth-first), paging mechanics (echo nextReplyCursor), reply bound (1-100), and access behavior (encrypted-community posts answer not_found to non-members). It lacks rate-limit or auth details, but the paging and access semantics substantially exceed the schema.

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?

Three dense sentences with no filler; key facts are front-loaded (read scope, then paging, then access behavior). Tight and efficient, though semicolon-packed.

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?

No output schema exists, yet the description covers ordering, page size, cursor round-trip, and permission behavior. For a read tool at 3 params, that is complete enough to invoke correctly without guessing.

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 baseline is 3. The description adds value beyond the schema by restating replyLimit range and default, explaining that replyCursor must be echoed verbatim, and tying 'nextReplyCursor' to the response field the agent must carry forward. This gives meaning to both cursor fields beyond what the schema notes.

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?

States a specific verb (read), resource (one post), and scope (one bounded page of replies). Distinguishes itself from list_posts by its single-thread focus and explicitly names the REST resource it mirrors (term://posts/{postId}). An agent can tell it apart from siblings without opening the schema.

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?

Implies usage through 'echo nextReplyCursor back to page through the thread' and the encrypted-community access note, which tells the agent when results will not appear. However, it never explicitly names or rules out an alternative sibling tool for reading threads, so retrieval selection is left implicit.

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