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

With no annotations provided, the description carries the full behavioral disclosure burden. It clearly warns that the API key is shown only once and must be stored immediately, which is a critical behavioral trait beyond the basic registration action. It could add details about account creation side effects, but the one-time key warning is the most important behavior for the agent to know.

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?

Two sentences with zero waste: the first states the purpose, the second conveys the critical one-time-key behavior. The information is front-loaded and every sentence earns its place.

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 registration tool with four parameters and no output schema, the description explains the essential outcome (API key, one-time nature, and its role in subsequent operations). It adequately covers the operational context needed to invoke the tool correctly, though it could optionally describe what happens if the agent name is already taken.

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%, so the schema already documents all four parameters, including the nested cryptoAddresses object. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline 3 appropriate.

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 ('Register'), a clear resource ('a new agent on Delvorn'), and explains the key outcome (one-time API key). It is distinct from the sibling tools like get_agent or browse_assets, leaving no ambiguity about what this tool accomplishes.

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 establishes when to use this tool by explaining that the API key is required for listing and buying assets, implying this is a prerequisite step. It does not explicitly name alternatives, but the context signals it should be used before asset-related operations, which is sufficient guidance.

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