slack_lists_download_start

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

No annotations are provided, and the description only states 'Start a list download.' without disclosing whether the operation is asynchronous, returns a job identifier, or any side effects. The existence of an output schema suggests a return value, but the description does not hint at this, leaving behavioral expectations unclear.

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 a single sentence, extremely concise and front-loaded. It uses minimal words to convey the core action. However, it may be too lacking in detail for completeness, but for conciseness alone it scores high as it wastes no space.

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 tool has two parameters and an output schema, the description is incomplete. It does not explain the download process, whether it is synchronous, or what the output represents. Without annotations, more context is needed to fully understand the tool's behavior and usage.

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?

The input schema provides descriptions for both parameters (list_id and include_archived) with 100% coverage. The tool description adds no additional meaning beyond what the schema already offers. Parameter semantics are adequate but not enhanced by the description.

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 tool name 'slack_lists_download_start' combined with the description 'Start a list download.' clearly indicates the action (start) and resource (list download). It distinguishes itself from the sibling 'slack_lists_download_get', which likely retrieves the result of a started download. The purpose is unambiguous and specific.

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 provides no guidance on when to use this tool versus alternatives like 'slack_lists_download_get'. It does not mention prerequisites, such as requiring a valid list_id, or context for invoking a download. The agent is left without decision-support information.

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