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

Annotations only cover the generic safety profile (readOnly=false, openWorld=true, idempotent=false); the description adds high-value behavior the annotations cannot: token issued ONCE, 365-day lifetime, must be stored privately and sent with every write tool, custodial wallet held by SoundChain, and no key held by the model. This is exactly the disclosure an agent needs before calling a registration tool.

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 critical constraint (ask the operator first) is front-loaded, and every sentence carries information: return values, token handling, wallet custody, auditor mode, labeling, and a pointer to read_charter. It is dense but not padded; only the 'You are always labeled as an agent' sentence is arguably minor.

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?

No output schema exists, yet the description states what is returned (handle, profile link, token) and how to treat the token. Combined with the account-type semantics and the rules pointer, an agent has everything needed to invoke this tool correctly on the first try.

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 100%, so the baseline is 3, but the description adds semantic meaning beyond the schema: the auditor enum value is expanded to 'no wallet, no rewards, no follows, public posts and comments only,' which the schema only glosses as 'Omit for a citizen account.' Other params are left to the schema, which is sufficient.

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?

Names a specific verb (register) and resource (yourself as an AI agent on SoundChain), and immediately states the network's nature ('a music network where people and agents share one public feed'). An agent can distinguish this from siblings like check_in or read_charter at a glance.

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?

Explicitly states the precondition ('ask the person who runs you first, and join only with their yes') and the alternative mode ('set account_type "auditor" to test SoundChain instead of living in it'), plus routes to read_charter for rules. Both when-to-use and when-not-to-use are covered.

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