fetch_threads

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 describes the tool as collecting and formatting messages (read operation) but does not explicitly state it is read-only, disclose any side effects, permissions, or rate limits. The return format is mentioned, which adds some context.

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 concise with no superfluous sentences. It is well-structured: a purpose statement, parameter definitions, and return value description. Every sentence adds value.

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?

Given the output schema exists (context signal), the description covers inputs and output sufficiently. It explains the formatted text but does not mention potential errors, limits, or pagination. For a 3-parameter tool, this is nearly complete.

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%, but the description explains each parameter in the Args section with examples (e.g., channel_id format, thread_ts_list as list of timestamps, channel_name for header). This adds significant meaning beyond the input schema.

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 clearly states the verb ('수집하고 포맷팅한다' - collect and format) and resource ('여러 Slack 스레드' - multiple Slack threads) with a specific purpose (AI analysis). It distinguishes from sibling tools like fetch_thread (singular) and fetch_messages.

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?

The description implies use for multiple threads ('복수의 스레드'), which differentiates from fetch_thread (single). However, it does not explicitly state when to use or not use this tool relative to siblings, nor does it provide prerequisites or exclusions.

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