discord_send_webhook_message

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

The description adds useful behavioral context beyond the annotations: the token authorizes the send, no bot permissions are needed, content or embeds are required, and the message ID is returned. This meaningfully explains the operation's side effects and return value without contradicting the 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 compact and front-loaded: core action first, then feature highlights, then a critical validation rule, then the return value. Every sentence adds value and there is no redundant or vague wording.

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 the rich 100%-covered input schema and no output schema, the description provides the missing pieces: auth requirements, payload constraints, and return value. An agent has enough information to invoke this tool correctly and understand what to expect.

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 the baseline is 3. The description adds the important cross-parameter constraint that at least one of content or embeds is required, which is not enforced by the schema's required fields. It also summarizes the username/avatar overrides and 10-embed limit, though those are already in 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?

Description states the specific action: send a message through a webhook using its ID and token, with no bot permissions needed. This clearly differentiates it from bot-token message tools like discord_send_message and from webhook management tools like discord_edit_webhook. The resource and mechanism are unambiguous.

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 gives clear context for when to use this tool: when you have a webhook ID and token and do not need bot permissions. It does not explicitly name alternative tools or state when not to use it, but the auth distinction makes the intended usage fairly evident.

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