webhooks

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

With no annotations provided, the description carries the full burden. It does add genuine behavioral context: deliveries are HTTPS POSTs triggered by named events such as message.delivered. But it is silent on authentication/secret verification, retry and failure behavior, whether delete is irreversible, and what the create/get responses contain for a tool that also supports mutation and deletion.

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 one-line purpose is front-loaded, followed by a compact action list and a single concrete example. The `get / update / delete: standard CRUD` line is slightly redundant but earns its place by covering three actions in one clause. No filler sentences.

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 7-parameter tool with no annotations and no output schema, the description covers the essential what-and-which-action but omits auth requirements, deletion consequences, pagination, and return shape. Adequate for selecting the tool, thin for invoking it safely.

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 description coverage is 0% across 7 parameters, so the description must compensate. It meaningfully explains `url` and `events` through the create example and gives the `action` enum values verbatim, but `skip`, `limit`, `status`, and `webhook_id` are never mentioned, leaving pagination and enable/disable semantics undocumented.

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 states a specific resource and effect: registering URLs to receive HTTPS POSTs on Blueticks events. It then enumerates the five supported actions, so an agent immediately knows this is a multi-action webhook CRUD tool. It does not explicitly contrast itself with siblings, but the resource is distinct enough from chats, campaigns, and audiences that confusion is unlikely.

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 action list implicitly routes an agent to the correct sub-operation, and the create example shows the shape of a registration request. However, there is no guidance on when a webhook is the right tool versus polling or the other sibling resources, and no prerequisites such as required scopes or signing-secret setup.

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