slack_list_files

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

No annotations exist, so the description must bear the full burden. It fails to disclose any behavioral traits such as whether the tool is read-only, what data is returned, pagination behavior, or authentication requirements (beyond a generic routing note).

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 very short and front-loaded, but the brevity comes at the cost of content. Every sentence is present but offers limited actionable information. It is concise in length but not in providing 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 tool has a parameter and an output schema (not shown), the description should at least mention what the tool returns. It does not. The context is incomplete; the agent has no clear picture of the tool's behavior or output.

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 compensate. It only says 'arguments: JSON string of arguments for the connector operation,' which adds minimal value. It does not explain the expected structure or keys, leaving the agent without meaningful guidance.

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 name 'slack_list_files' strongly implies listing Slack files, but the description only reiterates the name as 'Slack connector operation list_files' without specifying scope (e.g., files from a channel, user, or workspace). The description lacks a clear verb and resource distinction, making it slightly vague.

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?

No guidance is provided on when to use this tool over sibling tools like slack_files_info or slack_files_delete. The description does not mention use cases, context, or exclusions. The routing information is generic and does not help the agent decide.

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