slack_open_dm

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

Annotations already provide readOnlyHint=false, idempotentHint=true, and destructiveHint=true, so the description is not required to restate those. It does add value by describing governance routing, Spring's verification of the claimed effect, and the approval_ref requirement for resuming writes. However, it does not disclose what the Slack operation actually changes or what the destructive behavior entails.

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 compact and uses a clear labeled argument list. The opening line is somewhat redundant with the tool name, but it quickly establishes the platform mapping. Most lines are informative and the structure is easy to scan.

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?

For a connector wrapper, the governance and approval context is covered, but the domain-level behavior is missing: an agent still does not know what `open_dm` does in Slack or how to construct a valid `arguments` JSON payload. The output schema exists, but input usability is severely limited without knowledge of the underlying Slack API contract. This is incomplete for correct invocation.

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?

Schema description coverage is 0%, so the description carries the burden of explaining parameters, and it does provide brief definitions for project_id, project_ref, connector_account_ref, idempotency_key, effect, and approval_ref. The critical `arguments` parameter, however, is only described as a 'JSON string of arguments for the connector operation' with no indication of what fields the Slack operation expects. This partial compensation earns a middle score.

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 names the platform tool `slack.open_dm` and calls it a 'Slack connector operation', but it never explains what the operation actually does beyond the name. It does not describe the Slack-level outcome, such as which user or conversation is involved. This is closer to restating the tool title than providing a functional purpose.

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?

There is no guidance on when to use `slack_open_dm` versus alternatives like `slack_open_modal`, `slack_post_message`, or other Slack tools. The description mentions routing and governance constraints but not the practical conditions under which this tool should be selected. No exclusions or alternative references are provided.

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