Webhook Deliver

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

The annotation destructiveHint: true indicates the operation is destructive. The description adds no further behavioral details (e.g., rate limits, authentication requirements, failure modes). Since annotations cover the key behavior, the description's contribution is minimal.

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 a single, effective sentence with no extraneous words. It front-loads the action and platforms, making it easy to parse.

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?

The tool has four required parameters and no output schema. The description does not explain the return value or error handling. While the schema is complete, the description could be more informative about the response, but given the tool type (sending a message), it may be acceptable.

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 100% with clear parameter descriptions. The tool description does not add any additional meaning to the parameters; it only mentions the platforms in a generic way. Baseline of 3 is appropriate as the schema already does the work.

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 sends a message via webhook to Teams, Slack, or Discord, and specifies use cases (status reports, alerts, notifications). This clearly distinguishes it from sibling tools, none of which are messaging 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?

The description provides explicit usage context: status reports, alerts, and notifications. It does not specify when not to use or mention alternatives, but given the sibling list, no alternative exists for this function.

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