Send a test notification

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

Discloses that it posts messages to Slack or Discord and returns ok=true. Annotations already indicate non-destructive mutation, but description adds specific platform behaviors.

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 covering purpose, kinds, usage, and return value. No wasted words. Front-loaded with action.

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 one-param tool with no output schema, description covers purpose, usage context, parameter semantics, and return value. Complete.

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 has one param with enum and description. Description adds significant meaning by explaining what each kind does (Block Kit message for slack, posts to webhook for discord), which is beyond the schema.

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 the verb (send), resource (test notification to channel), and scope (for project). Differentiates from siblings by specifying supported kinds and their behaviors.

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 says 'Use this to verify the integration is working after setup or after changing credentials.' While no alternatives or when-not-to-use are given, the context is clear for a test tool.

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