Create domain

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

With no annotations, the description carries the transparency burden. It discloses that working routing requires specific parameters and that verification is a separate step, but does not mention side effects, permissions, or reversibility. It adds some context beyond the basic create operation.

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 four concise sentences, front-loaded with purpose, includes a concrete example, and contains no unnecessary words. Every sentence adds value.

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 creation tool with nested objects and no output schema or annotations, the description adequately covers the main purpose, the required parameter, the prerequisites for working routing, and the next step. It does not explain return values, but no output schema exists, and the schema covers nested property requirements.

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 low (33%), so the description supplements by explaining the 'name' parameter with an example and noting the importance of fallback_url and store URLs. However, it does not detail all nested required fields, leaving some gaps that the schema descriptions partially fill.

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 states a specific verb and resource: 'Create a DeepTap subdomain' and 'configure iOS Universal Links and/or Android App Links.' This clearly distinguishes the tool from siblings like update_domain, verify_domain, and get_domain.

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 provides clear context for when to use the tool (creating a new subdomain) and gives a follow-up step ('After creating, call verify_domain'). It also notes conditions for working routing, but does not explicitly mention alternatives or exclusions.

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