Slack send

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

Annotations already communicate destructive/side-effect behavior, and the description's 'Post a message' aligns with that. However, it adds little extra behavioral context such as channel visibility, auth requirements, or that posting is irreversible.

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?

'Post a message' is concise and front-loaded, but 'Prompts.' is a cryptic fragment that does not earn its place and should be removed or expanded.

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 simple two-parameter send tool with an output schema and annotations, the core action is clear enough to be minimally viable. Yet the missing parameter semantics and lack of usage guidance leave meaningful gaps for an agent deciding how to invoke it correctly.

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 needed to compensate, but it only says 'Post a message.' It does not explain channel format (ID vs name), text length, or other constraints beyond the schema's basic property names.

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 a clear action, 'Post a message,' with the resource implied by the tool name slack_send. It distinguishes from sibling send tools like slack_list, though the 'Prompts.' fragment is vague and detracts slightly.

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 about when to use this tool versus alternatives, or mention of exclusions. An agent must infer from the name and sibling list that slack_send is for sending rather than reading.

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