discord_send_webhook_message

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

With no annotations, the description must carry the behavioral disclosure burden, but it only states 'sends a message' without mentioning any side effects, requirements for webhook validity, rate limits, or how optional parameters like threadId or username affect behavior.

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 single sentence is concise and front-loaded with the key action, containing no fluff. However, it is structurally minimal and omits necessary parameter details, so it doesn't fully earn a 5.

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 tool with 6 parameters and no output schema or annotations, a one-sentence description is insufficient. It doesn't explain how webhook credentials are obtained, when to use this over discord_send, or any usage context.

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?

The input schema has 0% description coverage and the description provides no parameter explanations. All six parameters, including the required webhookId, webhookToken, and content, are left undefined, forcing the agent to guess their meanings from names alone.

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 states a specific verb ('Sends'), a resource ('a message to a Discord channel'), and the distinguishing method ('using a webhook'). This differentiates it from siblings like discord_send, which likely uses a bot, and from webhook management tools.

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 choose this webhook-based tool over alternatives like discord_send. There are no prerequisites, exclusions, or alternative tool references.

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