webhooks_execute

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

Beyond the annotations (readOnly=false, openWorld=true, idempotent=false, destructive=false), the description adds critical behavioral context: the special auth requirement (no `Authorization: Bot` header), the low-level V2 validation being `z.record`, query params being passed in the URL not body, and return behavior for `wait:true` vs otherwise.

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 well-structured with bold section headers and bullet-like lines. Every sentence serves a purpose: purpose, when to use, alternatives, auth caveat, required payload note, and return contract. It is appropriately sized for a complex escape-hatch tool.

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 tool's complexity (18 params, nested objects, special auth, low-level escape hatch), the description covers the essential context: auth constraints, query param placement, required fields, and return values. The presence of an output schema does not obviate the need for these behavioral details, and they are all included.

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 description adds vital parameter semantics beyond the schema by explaining that `wait` and `with_components` are URL query params, that at least one of `content`, `embeds`, `components`, `attachments`, or `poll` is required, and that V2 component layout validation is intentionally loose (z.record). These nuances are not inferable from the input schema 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 clearly states the tool's purpose: 'Execute (send a message through) a webhook.' It further distinguishes itself with 'Low-level escape hatch' and explicitly points to `messages_send` and `components_v2_send` as alternatives, making its role among siblings 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?

Provides explicit 'When to use' and 'Prefer instead' sections with named alternatives (`messages_send`, `components_v2_send`). It also states the prerequisite of holding the token, which is actionable guidance for choosing this tool.

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