slack_open_dm

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

With no annotations, the description carries full burden. It only mentions routing details (JWT, tenant scope) but nothing about side effects, permissions, return values, or safety characteristics. The agent gets no behavioral insight.

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 wastes space on low-value routing details upfront. It does not front-load the core purpose and includes syllables that earn their place.

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 complexity (a simple Slack DM opener) and the existence of output schema, the description fails to provide any essential context. It does not differentiate from siblings or explain return values, leaving the agent underinformed.

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 single parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which is redundant with the schema and adds no meaning. The schema description coverage is 0%, and the description does not specify what keys or values the JSON should contain.

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 says 'Slack connector operation `open_dm`' but does not explain what opening a DM means in Slack. The purpose is vague; it relies solely on the tool name to hint at functionality, lacking a clear verb and resource description.

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 versus alternatives like slack_post_message or slack_create_channel. The description gives no context about prerequisites, typical scenarios, or exclusions.

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