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

With no annotations, the description carries the full burden and does well: it discloses the return shape, that `parent` is null for top-level posts, level-by-level ordering (oldest first), tree reconstruction via parentTxid, and hard truncation limits of 500 replies / 10 levels. It does not mention read-only safety, auth requirements, or behavior for a missing/invalid txid.

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?

Front-loaded with the purpose in one sentence, followed by a dense but useful return-value clause. The second sentence is long and packs several facts, but every element earns its place; 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?

No output schema exists, so the description must explain return values, and it does so fairly completely, including field meanings and truncation flags. Remaining gaps are minor: error handling for an unknown txid and whether post objects carry full author/profile data.

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 100% with a single parameter, so the baseline is 3. The description adds only that the txid identifies 'the requested post' (the parent post of the thread), which is a minor clarification beyond the schema's 'Txid of the parent post.'

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 and resource: 'View a post and all its replies as a conversation thread,' which is clearly distinct in scope from a flat post lookup. It does not name or contrast with siblings like peck_post_detail or peck_user_posts, so an agent must infer the boundary rather than being told it.

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 by the purpose (fetch a conversation tree when you need replies), but there is no explicit when-to-use, when-not-to-use, or named alternative. The 500-reply/10-level truncation note hints at a scale limit but does not say what to do instead (e.g., paginate or use another tool).

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