Create webhook

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

Annotations already declare readOnlyHint=false and destructiveHint=false, consistent with a create operation. The description adds context about webhook behavior (display name/avatar) but does not disclose additional caveats like required permissions or the returned webhook object. The added context is useful but modest.

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 long, front-loaded with the action ('Create an incoming webhook on a channel'), and every word earns its place. No filler or 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?

For a simple create operation, the description plus schema covers the essential context: purpose, channel, name, avatar, and guild. It lacks explicit return value info, but given the annotations and simplicity, this is acceptable. The description is nearly complete for an agent to use correctly.

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 schema provides descriptions for 3 of 4 parameters (75% coverage), with only 'name' lacking a description. The description's mention of 'display name and avatar' gives conceptual meaning to the name and avatar_url parameters, but it does not add detailed parameter semantics 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?

The description clearly states 'Create an incoming webhook on a channel' – a specific verb and resource. This distinguishes it from sibling tools like update_webhook, delete_webhook, and send_webhook_message, making the purpose 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 implies the use case by explaining webhooks post with any display name and avatar, which is how messages 'as someone' work legitimately. However, it does not explicitly mention when to use this tool versus alternatives like send_webhook_message, nor does it state prerequisites or exclusions.

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