Read a whole conversation

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

Beyond the annotations (read-only, idempotent, non-destructive), the description reveals the flattening behavior, the parent-naming format, the recursive scope, and the ownership restriction. This is useful behavioral context, though it does not cover response pagination or error conditions.

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 sentences, each with distinct value: the core behavior, the ownership constraint, and the practical use case. 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?

With no output schema, the description gives a sufficient mental model of the return value (flattened list with parent naming) and the intended decision context. Minor gaps remain around 'reverse', pagination, and how this differs from get_replies/get_all_replies, but these are partially covered by the schema.

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 description coverage is 80%, so the schema already documents id, limit, cursor, and account. The description adds only that the post must be owned, which the id schema already states. It does not compensate for the undocumented 'reverse' parameter.

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 names a specific resource (a whole conversation under one of your posts) and a concrete behavior (every reply including replies-to-replies, flattened, with each reply naming its parent). It is clear but does not explicitly contrast with sibling tools such as get_replies or get_all_replies, so it stops short of full differentiation.

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 provides clear usage context: 'Only works on posts you own' and 'This is what to read before deciding what deserves an answer.' It does not, however, state when to prefer this over get_replies/get_all_replies or give exclusions.

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