Register Domain

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

No annotations are present, so the description carries the full burden. It discloses a precondition (SUBREG_READONLY=false) and a units detail (period in years). However, it does not describe side effects such as billing, propagation, or whether registration is immediate, nor does it mention error conditions or return behavior.

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 three sentences long, front-loaded with the core purpose, and each sentence adds distinct value: purpose, prerequisite, and parameter semantics. No redundancy or filler.

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 an 8-parameter tool with no output schema, annotations, or schema descriptions, the description is incomplete. It omits what the tool returns, the meaning of nsset and ns_hosts, and any guidance on checking domain availability first (check_domain is a sibling). These gaps leave the agent underinformed for a complex operation.

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 0%, so the description compensates by explaining that registrant_id/contacts_admin_id/contacts_tech_id/auth_id are Subreg contact object ids and references info_contact/contacts_list. It also clarifies period is in years. Though nsset and ns_hosts remain unexplained, most non-obvious parameters are covered.

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 'Register (order) a new domain' – a specific verb and resource. The parenthetical '(order)' clarifies the commercial nature and helps distinguish from sibling tools like renew_domain and delete_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?

The description provides a clear prerequisite: 'Requires SUBREG_READONLY=false', indicating when the tool can be used. It also implicitly defines usage context (registering a new domain) but does not explicitly reference alternatives like check_domain for availability or renew_domain for renewals.

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