Create domain

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

With no annotations provided, the description must carry the behavioral burden. It explains the verification process and notes that limits are plan-dependent, but does not mention potential failure modes, rate limits, or side effects. This is adequate but not exhaustive.

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 description is two sentences, front-loaded with the core purpose. Every clause adds value: the first sentence defines the action, the second details verification options and a plan caveat. 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 the tool's complexity (7 parameters) and lack of output schema, the description covers the key operational aspects: domain addition, verification flows, and plan-dependent limits. It references relevant sibling tools for TXT records, making it complete for an AI agent, though it omits details on return values or error handling.

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%, setting a baseline of 3. The description adds meaningful context beyond the schema by explaining the default verification method ('mx') and the prerequisite for 'txt' verification via get_domain_dns_record. This enhances parameter understanding.

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 description clearly states the action: 'Add a domain to the postale.io account.' The verb 'Add' plus the resource 'domain' makes the tool's purpose unambiguous. It also distinguishes itself from sibling tools by focusing solely on domain creation, with details on verification methods.

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?

The description provides clear guidance on when to use each verification method, including a prerequisite instruction to call get_domain_dns_record for TXT verification. It does not explicitly mention when not to use the tool or compare it to alternative tools like update_domain, but the context is solid.

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