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

Annotations already declare a non-read-only, non-destructive, non-idempotent write; the description adds real value beyond them by disclosing the one-time API key return, that registration is free, and that it grants no trust or Directory claims. It stops short of stating what happens on repeat calls, though 'one-time API key' hints at the non-idempotent nature.

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 tight sentences with the core action front-loaded and the caveats following. Slight jargon density ('canonical Registrar', 'Directory entries') but no wasted 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?

Effectively complete on purpose, side effects, and return (one-time key) despite no output schema, but with 0% parameter coverage the description leaves the four optional inputs unexplained. For a 5-param mutation tool that is a clear gap.

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 coverage is 0% and there are 5 parameters, yet the description explains none of them. The agent is left guessing what 'wallet', 'endpoint', 'framework', and 'capabilities' mean or how they affect registration, which is a significant gap for a multi-param tool.

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?

States a specific verb (Register) and resource (OmniDome member identity), and is clearly the only write/registration tool among the discover_/read_/check_ siblings. 'Through the canonical Registrar' is a bit of internal jargon but doesn't obscure the action.

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?

Implied use case is clear (obtain a member identity and API key), and the description helpfully scopes what registration does NOT do (no auto-claim of Directory entries, no trust). However, it never explicitly says when to call this versus the sibling discovery tools or what prerequisites exist.

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