Disposable Email Checker

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

No annotations are provided, so the description carries the full disclosure burden. It does add real value by naming the return tuple ({ domain, disposable, source }) and by qualifying the check as against a 'known' list, implying finite coverage. It does not say whether this is a local list vs a network call, whether the provider list is exhaustive or maintained, or how a malformed input is handled.

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?

Two sentences, zero filler: the first states the check and its scope with illustrative examples, the second states the return shape. Purpose is front-loaded and nothing is redundant.

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 single-parameter, read-only lookup with no output schema, naming the three returned fields is exactly the information the schema cannot supply. The only remaining gap is that 'source' is never defined (which provider list or data set produced the verdict) and no failure/coverage caveat is given.

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 the single parameter's own description already explains it accepts 'an email address (user@domain.com) or a bare domain'. The tool description restates that dual-input acceptance but adds no syntax, format, or edge-case detail beyond the schema, so the baseline of 3 is correct.

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 precise verb and resource ('checks whether an email address or domain belongs to a known disposable/temporary email provider') and backs it with concrete provider examples (mailinator.com, 10minutemail.com). An agent can tell exactly what the tool answers without opening the schema, and no sibling tools exist to confuse it with.

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?

Usage is implied by the narrow scope of the purpose statement — validate an address/domain before accepting it — but there is no explicit when/when-not guidance, no mention of alternatives (e.g. general email validation), and no note on limits of the provider list. With no siblings this is adequate, not rich.

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