test_destination

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

Beyond the annotations, the description discloses the default synthetic LastPing alert behavior, the 400 error for non-email destinations with resend_verification, and the idempotent verified-state behavior. The idempotentHint=false annotation is not contradicted because the default test-alert path is not idempotent, while the description specifically limits idempotency to resend_verification on verified destinations.

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 dense but every sentence carries decision-relevant information, and the core action is front-loaded in the first sentence. The length is justified by the two-mode behavior (test alert vs. resend verification) that the agent must distinguish.

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 tool with two modes, no output schema, and a closely related create_destination sibling, the description covers invocation, mode selection, error conditions, and repeat safety. An agent can decide whether to call this tool and with which flag without needing additional context.

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 the schema already documents both parameters, including id source, the instead-of-test-alert behavior, email-only restriction, 400 error, and idempotency. The description repeats this semantic context but does not add new parameter-level meaning beyond the schema, so the baseline score 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?

The description states a specific action and resource ('send something through a destination') and the intended outcome ('move it from created to known to work'). It distinguishes this from create_destination and other destination siblings by positioning it as the post-creation verification step.

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?

It explicitly tells when to use the default test alert ('after create_destination to confirm the credentials are right') and when to use resend_verification instead (when create_destination reported UNVERIFIED and the confirmation email never arrived or expired). It also warns that a test alert is useless for unverified email destinations, giving a clear exclusion.

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