conversations_replies

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

readOnlyHint=true already establishes the safety profile, so the description's main additions are the CSV output format and the thread_ts identifier format with an example. It says nothing about ordering, completeness of the reply set, or why include_activity_messages exists, so behavioral context beyond annotations is thin.

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 short sentences with the output format front-loaded and no filler. The cross-reference for limit/cursor is compact, though '1d' default on limit goes unexplained and slightly undercuts the terseness.

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?

An output schema exists, so return values need no explanation, and annotations cover safety. However, with a required channel_id and a non-obvious include_activity_messages flag documented nowhere, the description is not complete enough for confident invocation.

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 0% across 5 parameters, so the description must carry the load. It usefully defines thread_ts with an example and points to conversations_history for limit/cursor, but channel_id (required) and include_activity_messages are entirely unaddressed, leaving a meaningful gap.

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 states the resource and shape of the result clearly ('A thread (parent plus replies) as CSV'), which distinguishes it from the channel-wide conversations_history. It lacks an explicit verb, but the operation (retrieve a thread) is unambiguous.

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 defers to conversations_history for limit/cursor semantics, implying the same paging model, but never states when to pick this tool over conversations_history, conversations_search_messages, or conversations_add_message. Usage is only inferable from the tool name and the 'thread' framing.

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