slack_files_delete

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

No annotations provided, so the description must compensate, but it only includes routing details (JWT, tenant, scope). It does not disclose irreversibility, permissions, or output behavior, despite the output schema existing.

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 short but includes routing information that may be unnecessary for tool selection. It could be more front-loaded with the core action.

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's simplicity (delete operation), the description is incomplete. It fails to specify the required arguments structure, making it difficult for the agent to use correctly, even though an output schema exists.

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 'arguments' parameter is described as a 'JSON string of arguments for the connector operation', but the schema has 0% coverage and no documentation of required fields (e.g., file_id). The agent cannot infer what to put in the JSON.

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 states it's the 'files_delete' Slack connector operation, which implies file deletion, but it does not explicitly state the verb and resource (e.g., 'Deletes a file from Slack'). The name helps, but the description is 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 on when to use this tool versus other Slack file tools (e.g., slack_files_info, slack_list_files). No context on prerequisites or when to avoid using it.

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