create_webhook

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

No annotations are provided, so the description fully discloses behavioral traits: validation GET request during creation, max 10 concurrent requests, respects read-only and dry-run modes, and error conditions (URL validation failure). This covers safety and side effects comprehensively.

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 well-structured with a clear introductory sentence, side effect, usage guidelines, and parameter details. It is somewhat lengthy but every sentence adds value. Could be slightly tighter, but still very good.

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 zero schema coverage, no annotations, and 4 parameters, the description covers all essential aspects: parameters, side effects, usage guidelines, return structure, and error handling. It is complete for an agent to select and invoke the tool 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?

Input schema has 0% description coverage, so the description must explain all parameters. It does so: list_id (10-char alphanumeric, source from list_audiences), url (public HTTPS, must return 200 on GET), events and sources (comma-separated, defaults all). It also describes return structure.

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 tool creates a webhook for HTTP POST notifications on audience events, with a specific verb and resource. It distinguishes itself from siblings like list_audience_members and campaign reports by explicitly stating when not to use it.

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 not to use the tool (for polling or batch data retrieval) and provides alternative tools (list_audience_members, campaign reports). Also mentions authentication and max concurrent requests.

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