register_domain

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

With no annotations, the description carries full burden. It discloses that registration happens in the browser, the website handles the order, the user signs via wallet there, and the MCP does NOT build/broadcast payment. This gives important behavioral context beyond simple 'get link'.

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 concise sentences: purpose, browser-flow clarification, and usage trigger/parameter guidance. Every sentence earns its place with no fluff or repetition.

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 simple link-generation tool with 2 params and no output schema, the description covers purpose, mechanism (browser), what it does NOT do (payment), when to use it, and the optional refcode. It is sufficiently complete for an agent to select and invoke correctly.

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% for both domain and refcode, so baseline is 3. The description adds a conditional usage note for refcode ('Pass refcode if a referral applies'), but this closely mirrors the schema description, offering minimal added meaning.

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 tool 'Get the link to register' with specific TLDs (.xrp/.xrpl/.xrpfi/.rlusd) on xrpdomains.xyz. This is a specific verb+resource and differentiates from sibling tools like check_domains or recommend_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?

Provides explicit trigger examples ('Use when the user says "register X.xrpfi" or "buy X.xrp"') and clarifies the MCP does NOT build or broadcast payment, implying when not to expect full transaction handling. It doesn't explicitly name alternative tools but gives clear usage context.

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