slack_list_files

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds valuable context beyond that: newest-first ordering, required OAuth scope, filter semantics, and pagination behavior ('the reply says how many pages there are') – all useful behavioral details not present in the schema.

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?

Front-loads the core action ('List files, newest first') and then delivers scoping, filters, and pagination details in a dense but efficient manner. Every sentence contributes information, though the shorthand style is slightly terse.

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 an output schema exists, the description needn't explain return values. It covers ordering, filters, types, pagination, and auth scope, which is sufficient for an agent to invoke the tool correctly. The only notable omission is any mention of the required workspace parameter, but the schema marks it required and its meaning is conventional.

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?

With 0% schema description coverage, the description must carry parameter meaning. It explains types (with a concrete list of values), page (1-based), channel_id, and user_id well, but completely omits the required workspace parameter and the count parameter, leaving significant gaps.

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 and resource ('List files, newest first') and names the underlying API method (files.list), so the operation is unambiguous. It does not explicitly differentiate from siblings like slack_search or slack_file_info, but the listing scope is clear enough to distinguish it.

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 an important precondition ('needs files:read') and explains the intended filtering use case (by channel_id and/or user_id). However, it never states when to prefer this over alternatives such as slack_search or slack_file_info, leaving usage guidance implied rather than explicit.

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