webdev_webhook_tester

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description goes far beyond: states each call hits the target and may mutate remote state, lists blocked targets (private, localhost, .local, reserved-IP), no redirects, body limit 128 KiB, max 32 headers, timeout 15s, and detailed rate limits with CAPTCHA condition. Provides comprehensive behavioral constraints.

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 fairly long but well-structured: starts with purpose, then details on methods/headers/body, use cases, constraints, and limitations. Every sentence adds value, but some minor redundancy could be trimmed. Still, it maintains good readability and front-loads key information.

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?

Given 4 parameters (1 required, enum, nested object) and an output schema, the description covers all critical aspects: behavior, allowed inputs, restrictions, rate limits, and alternatives. The output schema exists so return values are not needed in description. It is complete enough for an agent to correctly select and invoke the tool.

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?

Input schema coverage is 100%, but the description adds meaningful context: method defaults to POST, body is only sent with POST/PUT/PATCH, headers description blocks specific headers and strips CR/LF, and the url description mentions rejection of private/localhost targets. While the schema already details parameter constraints, the description reinforces and adds nuance, so score 4.

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 it is a webhook tester that sends outbound HTTP requests and returns live responses. It lists supported methods, custom headers, and body usage. It distinguishes itself from sibling tools like network_request_headers, network_website_status_checker, and webdev_user_agent by specifying their different use cases.

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?

Explicitly states when to use: 'Use this to verify a webhook receiver or HTTP endpoint end-to-end'. Provides clear alternatives: 'use network_request_headers to only view request headers, network_website_status_checker for a plain status/uptime probe, or webdev_user_agent to parse a UA string'. Also notes that it is not idempotent and may mutate remote state, guiding appropriate usage.

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