Test webhook

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the agent knows this is a non-destructive, non-idempotent outbound action. The description adds that it dispatches a test event to an external endpoint, which is useful context, but says nothing about the payload sent, whether delivery attempts are logged, or whether repeated calls trigger repeated deliveries.

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?

A single well-formed sentence that front-loads the action and resource with no redundant or filler content.

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 one-parameter diagnostic tool with no output schema, the description is nearly sufficient; annotations cover the safety profile. A brief note on what the test produces (e.g., success/failure indication) would make it complete.

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 100% and there is only one parameter, so the schema already documents webhookId. The description adds no syntax, format, or meaning beyond what is in the schema, which is the expected baseline here.

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?

States a specific verb ('send') plus resource ('test event to a webhook endpoint') and the goal (verify configuration). An agent can distinguish it from sibling mutation tools like tailscale_create_webhook or tailscale_update_webhook, though it does not name them explicitly.

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 phrase 'to verify it is configured correctly and receiving events' implies the diagnostic use case, but there is no explicit when-to-use guidance, no when-not-to-use, and no mention of alternatives or prerequisites (e.g., webhook must already exist).

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