Verify Domain

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

Description adds that it 'may update ShipMail verification state', which is beyond annotations. Annotations do not declare mutation, so this is valuable. However, no detail on conditions or side effects.

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, front-loaded with action and purpose. No wasted words.

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?

Given low parameter count, existing annotations, and presence of output schema, the description covers core purpose and side effect. Could mention typical use case or result format but not required.

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% with clear descriptions for both 'id' and 'idempotency_key'. Description adds no further parameter insight beyond schema.

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?

Description uses specific verb 'Check' and identifies resource 'DNS and outbound verification for a domain'. It distinguishes from sibling domain tools like shipmail_get_domain or shipmail_get_domain_dns_records by focusing on verification and potential state update.

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?

No guidance on when to use this tool versus alternatives like shipmail_get_domain_dns_records. Description does not specify prerequisites or when not to use.

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