slack_me_message

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

With no annotations, the description should disclose behavioral traits. It only mentions routing and JWT scope, not what the operation does or any side effects, leaving the agent uninformed about the tool's impact.

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 (two sentences plus a parameter line) and front-loaded with name/routing, but it lacks substance. It is not verbose but fails to convey useful information efficiently, earning a middle score for conciseness.

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 complexity of Slack tools and many siblings, the description is severely incomplete. It does not explain the tool's purpose, when to use it, or how to structure arguments. The existence of an output schema is not leveraged.

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 only parameter `arguments` is described as a 'JSON string of arguments for the connector operation,' which adds minimal value over the schema. No details on expected keys or structure, leaving the agent without guidance on how to construct valid input.

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 a 'Slack connector operation `me_message`' but does not specify what the action does (send, retrieve, etc.) or the resource involved. The name suggests a self-message, but no differentiation from siblings like `slack_post_message` or `slack_open_dm`.

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 tools. The description lacks context for selection criteria or alternative suggestions.

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