Notify Slack

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

Discloses key behaviors: deliberate outbound egress (openWorldHint), no destructive mutation (destructiveHint false), no-ops on missing config/allow-list, and failure mode (returns warning, never throws). Adds context beyond annotations.

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?

Three sentences with no redundancy: immediately states action, explains scope, then clarifies edge cases. Front-loaded with core purpose.

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?

Covers all necessary aspects: input parameters, configuration dependency, no-op conditions, and error behavior. No output schema needed as return behavior is described.

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 67% with descriptions for text and event, but description adds behavioral context (e.g., event must be in allow-list) linking to parameters. Baseline 3 is appropriate.

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?

Clearly states 'Post a message to THIS project's user-configured Slack incoming webhook', identifying the tool as a Slack notifier specific to the current project, distinct from all sibling tools which cover other domains.

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?

Explicitly describes conditions for use: it only sends to the user-configured Slack webhook, no-ops when unconfigured or event not in allow-list. Does not list alternatives, but absence of other Slack tools makes this less critical.

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