automation_send_webhook

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

It adds useful behavior absent from the schema: the HTTP method is POST and the secret becomes an X-Webhook-Secret header only when provided. With no annotations, it still leaves operational behavior such as external side effects, errors, timeouts, and retries undisclosed.

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 single sentence is front-loaded with the core operation and contains no filler. The parenthetical efficiently communicates the optional header behavior.

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 three-parameter tool with an output schema, it covers the essential invocation and compensates well for undocumented parameters. Missing sibling-selection guidance and operational details leave clear gaps, especially because no annotations are supplied.

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?

Despite 0% schema description coverage, the description supplies meaning for all three parameters: the URL is the webhook destination, the payload is JSON, and the optional secret controls the named header. It does not add URL validation, payload constraints, or secret-handling details.

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), resource (JSON payload), and destination (webhook URL). It does not explicitly distinguish this specialized tool from the sibling automation_http_request.

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?

There is no explicit when-to-use or when-not-to-use guidance, prerequisite information, or alternative-tool recommendation. In particular, it does not explain when to choose this tool over automation_http_request.

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