Create webhook

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

The description adds behavioral context that webhooks can post with any display name and avatar, which is how 'as someone' messages work, and annotations confirm it's a write operation (readOnlyHint=false) with no contradiction.

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?

Two efficient sentences: one for the action, one for the behavioral insight, with no 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?

Missing details like required permissions, return value (webhook URL), and limitations; for a creation tool with no output schema, more context is needed.

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 75%, and description does not provide additional parameter details beyond the schema, though it gives context for the avatar_url parameter's purpose.

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 tool creates an incoming webhook on a channel and explains the legitimate use case for posting messages with custom names/avatars, distinguishing it from siblings like send_webhook_message.

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 when to use (to enable posting messages as someone) but does not explicitly state when not to use it or compare it to alternatives like send_message or send_dm.

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