Register a domain

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

With no annotations, the description carries the full burden. It discloses what it returns (tenant id and DNS TXT record), that it does not start crawling, and that it should be called only once. It doesn't cover error cases (e.g., duplicate domain) or side effects beyond registration, but the core behavior is clearly explained.

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?

Three sentences, front-loaded with the primary action and outcome. Every sentence earns its place – the second sentence prevents a common misuse (starting crawl prematurely), the third enforces idempotency. Zero fluff.

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 2-parameter tool with no output schema and no annotations, the description covers the essential flow: what it returns, the DNS verification step, and the retry guidance. It could mention duplicate-domain handling or error responses, but the tool is simple enough that these gaps are minor.

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 description coverage is 100% – both 'domain' and 'pages' are fully documented in the schema. The description adds no extra parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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 opens with 'Register one domain and return its tenant id plus the DNS TXT record' – a specific verb, resource, and output. It also distinguishes itself from sibling answerhatch_start_crawl by stating 'The crawl does not start here', making its scope unmistakable.

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 explicit when-to-use guidance ('Call this once per site') and when-not-to-use ('if a crawl will not start, retry the crawl rather than registering again'). It also directs the agent to the correct next step: wait for DNS publication, then call answerhatch_start_crawl.

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