Test alert destination

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

Annotations cover the safety profile (destructive=false, openWorld=true), and the description adds value beyond them: the required write scope, what actually gets delivered ('LastPing test alert'), and the important side-effect clarification that a test alert does not verify an unverified email or let it join a route.

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 permission requirement, then the default behavior, then the alternate mode. No filler; each clause carries invocation-relevant 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?

For a two-parameter action tool with no output schema, the description covers auth, payload semantics, both modes, and the key side-effect caveat. It stops short of describing the response an agent should expect, but that is a minor gap given the thorough coverage elsewhere.

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 the baseline is 3, but the description adds real meaning: it explains the default send behavior versus the resend_verification=true path and why you would choose the latter. It complements rather than repeats the schema.

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 ('Sends something through a destination now') and immediately qualifies it as a synthetic test alert rather than a real notification. This clearly separates it from create_destination, update_destination, and delete_destination without naming them.

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 explicit when-to-use for both modes: the default for confirming a new destination's credentials, and resend_verification=true for when a confirmation link never arrived or expired. It does not name alternative tools or state exclusions, but the context for invoking it is unambiguous.

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