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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the description correctly does not repeat the safety profile. It adds real value beyond them: the verification prerequisite and the fact that the response lists all email recipients afterwards. The one gap is that with idempotentHint=false it never says what happens if the same address is added twice.

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 action and effect, then the prerequisite workflow, then the return. No filler, and the ordering matches the order an agent needs the 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?

There is no output schema, and the description compensates by stating the return value ('every email recipient the form now has'). Combined with the two-parameter flat schema and existing annotations, an agent has everything needed to call it correctly on the first attempt.

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 a constraint the schema does not carry: the email value must be an already-verified address for the account. That materially changes how an agent fills the parameter rather than restating 'Recipient email address.'

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 plus resource ('Adds an email notification recipient to a form') and the effect ('so each submission is emailed there'). This distinguishes it cleanly from the other add_* destination siblings (slack, discord, webhook) without needing their schemas.

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 names the precondition (address must already be verified) and the exact recovery path: call bootform_add_verified_email first, wait for the click, check status via bootform_list_verified_emails, then call this. Names two siblings and the condition that selects each, leaving nothing to inference.

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