discord_send_webhook_message

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

Annotations indicate it is not read-only, destructive, or idempotent. The description adds behavioral context: authorization via token, requirement of content or embeds, and return of message ID. No contradictions with 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?

The description is two sentences, front-loaded with critical information (no bot permissions needed), and covers all essential aspects without redundancy.

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 no output schema, it mentions the return of the new message ID. It specifies the requirement of content or embeds, aligning with constraints. The tool's purpose is well-contextualized among sibling tools.

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 100%, so baseline is 3. The description mentions 'per-message username/avatar overrides' and 'up to 10 embeds,' which align with parameters, but does not add new meaning beyond the schema descriptions.

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 clearly states it sends a message via webhook, specifying key features like no bot permissions needed, username/avatar overrides, and up to 10 embeds. It effectively distinguishes from siblings like discord_send_message by emphasizing the token-based authorization.

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?

The description mentions 'no bot permissions needed — the token authorizes the send,' implying it should be used when webhook credentials are available. It provides clear usage context but does not explicitly list alternatives or when not to use, lacking full exclusion guidance.

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