webhooks_test

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false; the description adds real context beyond them — the call is synchronous with an immediate outcome, the payload is synthetic, and the delivery is persisted to delivery history. It does not note rate limits or what the returned outcome contains.

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?

Four short sentences, each carrying distinct information (sync behavior, payload type, precondition, side effect), with the core action front-loaded and no filler.

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?

No output schema exists, and the description only says the outcome is returned 'immediately' without describing what the result includes (status code, response body, latency). Otherwise, for a 3-parameter tool whose safety profile is covered by annotations, the definition is sufficient to call correctly.

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%, so uuid, companyId and eventType are already documented in the schema. The description reinforces the uuid (target endpoint) and default event type but says nothing about companyId or the env-var override behavior beyond what the schema states.

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 verb and resource — send a synchronous test delivery to a webhook endpoint — plus the distinguishing trait (synthetic webhook.test payload) versus the real delivery siblings like webhooks_deliveries. It is clear what the tool does, though it doesn't explicitly name an alternative tool.

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?

A concrete precondition is given ('The webhook must be active'), which implies usage for verifying endpoint configuration, but there is no explicit when-to-use/when-not or reference to sibling tools such as webhooks_deliveries or webhooks_update.

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