slack_read_thread

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

The 'Read' verb implies a non-mutating operation, which is useful since no annotations are provided. However, the description overstates 'all replies' while the schema caps replies at 200, and it does not disclose truncation, ordering, pagination, or auth requirements. Adequate but not rich.

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?

Two sentences: one establishes the operation and one tells the agent the required inputs. No fluff, and the most important information is front-loaded.

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?

For a simple read-only tool, the description plus a fully-covered schema provides enough to invoke it correctly: it names the operation, identifies the target resource, and points to the two required keys. It could add more about response shape or truncation, but those are partially covered by the limit parameter and the simple scope.

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%, so the schema already documents all four parameters. The description only restates that channel and the thread's parent timestamp are needed, adding no new format or behavioral detail beyond the 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?

States a specific verb ('Read'), resource ('replies in a Slack thread'), and the two identifying inputs. This clearly distinguishes it from siblings like slack_read_messages (channel-level reads) and slack_reply_thread (writing replies).

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?

Provides clear context: use this when you have a known channel and parent timestamp and need the thread replies. It does not explicitly name alternatives or exclusion cases, but the thread-specific scope is enough to route an agent correctly.

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