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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the bar is lower, yet the description adds real behavioral context: it returns a procedure rather than performing the test, and it explicitly states it will not fabricate provider event payloads. That 'what it does not do' disclosure is genuinely useful and beyond structured fields.

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?

Three sentences, front-loaded with the core purpose, then the procedure, then a rationale. The final sentence about not fabricating payloads is slightly tangential but earns its place by setting expectations about the tool's guarantee.

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 single-param read-only tool with full schema coverage and no output schema, the description is nearly complete: it explains what is returned, how to use the result, and its non-fabrication guarantee. Minor gap: it doesn't state the format of the returned procedure.

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?

One parameter with 100% schema description coverage that already warns never to pass the remote webhook endpoint ID. The description offers no additional parameter meaning, so the schema baseline of 3 applies.

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+resource: 'Return the exact test procedure for a destination.' Crucially, it disambiguates the misleading name by clarifying the tool returns a procedure rather than executing a test, and it names webhook_get_delivery_logs as a follow-up step. It doesn't fully contrast against the other webhook_* siblings (e.g. get_setup_guide), keeping it just below a 5.

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?

Gives clear context for when to use it: after creating a destination, generate a mock/test event with a Mock account (Test & Debug), then inspect webhook_get_delivery_logs and the target runtime. The workflow is spelled out, though there are no explicit exclusions or a named alternative to avoid.

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