Send webhook message

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that mentions are suppressed, which is a behavioral detail beyond annotations. However, it does not disclose other behavioral traits like rate limits, auth requirements, or side effects of overriding display name/avatar.

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 with no filler. First sentence conveys the core action and optionality, second adds a key constraint (mentions suppressed). Every word serves a 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?

With 6 parameters, no output schema, and sibling tools that overlap in sending functionality, the description is minimal. It omits details about return values, error handling, how to obtain or create a webhook, and does not explain the relationship to other send tools. Adequate but not comprehensive.

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 description coverage is 50%, and the description only mentions two optional parameters (display name and avatar override) which already have schema descriptions. It adds no meaning for the required 'webhook' parameter or key fields like 'content', 'guild', or 'embeds'. This does not compensate for the low coverage.

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 the action ('Post through a webhook') and the resource (webhook). It distinguishes itself from siblings like send_message and send_dm by specifying webhook and optional overrides. The note about suppressed mentions provides additional unique purpose context.

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 implies usage for webhook messages but does not explicitly contrast with alternatives like send_message (which sends as the bot) or when not to use this tool. No guidance on prerequisites or decision criteria is given.

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