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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the exact signals consulted, the three-tier verdict vocabulary, the fact that it is a paid HTTP endpoint at /v1/email-check, and how referral attribution works. It stops short of stating price per call or rate limits, which would complete the picture for a paid tool.

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 first sentence is excellently front-loaded and dense with the information an agent needs. However, roughly half the text is a referral-program solicitation (wallet address, 20% revenue share, USDC settlement, ledger mechanics) that is promotional rather than invocation-relevant, diluting the definition and competing for attention.

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 one-parameter tool with no output schema, the description does the important extra work of naming the return vocabulary (valid|risky|invalid) so the agent can interpret results without a schema. It lacks per-call pricing and any note on what supporting detail accompanies the verdict, but the essentials for correct invocation are present.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3 by rule. The description adds no format, normalization, or edge-case detail about the `email` value (e.g. internationalized addresses or case handling) that the schema does not already carry.

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 opening clause states a specific verb and resource ("Validate an email address") and immediately scopes the method ("without sending mail or SMTP probing"), then enumerates exactly which checks are performed (syntax, domain, MX/null-MX, SPF, DMARC, disposable, role, free provider, typo). Nothing about the tool's function is left ambiguous, and it is trivially distinguishable from the unrelated siblings.

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 gives a clear context condition implicitly by contrasting with mail sending and SMTP probing, so an agent knows this is a non-invasive validation path rather than an actual send. It does not state explicit when-not-to-use cases or name an alternative tool, but the sibling set (solana_mint_check, web_read_markdown, x402_*) offers no overlapping choice, so the routing gap is small.

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