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

Goes well beyond the annotations: it discloses that nothing is persisted as an inquiry, that recipients are fixed by admin settings and cannot be overridden, and gives concrete rate limits (once a minute per form, 20 a day per site). That is exactly the side-effect and throttling context an agent needs for a not-read-only, open-world call.

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?

Front-loads what the tool does, then side effects, then limits, then the usage guardrail — a sensible order with no filler in the first paragraph. The injection-warning sentence is somewhat boilerplate but justified for a notification-sending tool.

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 mutation with annotations covering safety and no output schema, the description covers purpose, side effects, recipient constraints, rate limits and consent gating. An agent has everything needed to call it correctly and avoid misuse.

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% and both parameters carry examples, so the schema does the heavy lifting; score sits at baseline. The description adds only the negative constraint that recipients cannot be supplied here, which helps scope but does not explain the form/site parameters.

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 and resource — sends a test notification to the form's configured recipients — and clarifies the important negative (it is not saved as an inquiry). It does not explicitly differentiate from near-neighbours like preview_mail or webhooks_test, which an agent would have to reason about from the resource name alone.

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?

A dedicated [When to use] block says to call it only when the user explicitly asks, and warns off prompt-injection from external data. It gives clear context but does not name alternatives such as preview_mail when the user merely wants to preview rather than send.

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