slack_post_ephemeral

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only mentions routing details ('Routes through /api/tools/invoke under your JWT, tenant, and company scope') but omits key traits such as message visibility (ephemeral vs permanent), required permissions, side effects, or rate limits.

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 unnecessary routing boilerplate that could be omitted. It is adequately concise but sacrifices content for brevity.

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 that the tool has an output schema (not detailed in the description) and only one parameter, the description fails to explain what the tool returns or how to properly invoke it. Important behavioural details are missing, making it insufficient for correct use.

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 coverage is 0%, so the description must compensate. It states that the 'arguments' parameter is a JSON string of arguments but does not specify which fields (e.g., channel, user, text) are expected, leaving the agent without actionable guidance.

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 merely restates the tool name ('Slack connector operation post_ephemeral') and does not explain what posting an ephemeral message means or how it differs from other Slack messaging tools like slack_post_message. This leaves the agent without a clear understanding of the tool's 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?

No guidance is provided on when to use this tool versus alternatives (e.g., slack_post_message, slack_me_message). The description lacks context for appropriate use cases or exclusion criteria.

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