slack_get_full_conversation

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

Annotations already declare readOnlyHint=true (safe read) and idempotentHint=true. The description adds only 'Can save to file' as behavioral context. It does not disclose potential slowness, rate limits, or behavior when the channel is very large. With annotations covering the safety profile, the description adds marginal value.

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, front-loaded with the main purpose. Every word earns its place. No fluff or redundancy.

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?

There is no output schema, so the description should clue the agent about what the tool returns (e.g., raw JSON, file path). It only says 'Can save to file' but doesn't describe the default output. Given 8 parameters and high complexity, the description is adequate but leaves gaps about return format and default behavior.

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 100%: all 8 parameters have descriptions in the input schema. The tool description does not add any extra meaning beyond what the schema already provides. For example, 'max_messages' default is only in schema. Thus baseline 3 is appropriate.

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 uses specific verbs 'Export FULL conversation history' and identifies resources (messages, threads, user names). It clearly distinguishes from siblings like 'slack_get_thread' which focuses on a single thread. The phrase 'FULL' implies completeness, setting it apart from partial history tools.

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 usage for full export but provides no explicit when-to-use or when-not-to-use guidance. No alternatives are named despite 20 sibling tools. The agent must infer usage from the tool name and description alone.

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