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

With no annotations, the description must carry the behavioral burden, and it does disclose useful traits: the payout cadence (weekly), the network/asset (Base USDC), and the destructive-ish null-to-clear semantics. It omits address-format validation, whether an existing address is overwritten, auth requirements, and when the new address takes effect — meaningful gaps for an unannotated mutation.

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?

A single front-loaded sentence with zero waste; the core action comes first and the null-clearing edge case is tucked into a parenthetical.

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 one-parameter mutation with no output schema and no annotations, the description covers the what, the parameter's meaning, and the clear case — enough to call it correctly. Missing permission/validation and effect-timing details keep it from being fully complete.

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%, so the description has to explain the single parameter, and it does: the value is a Base USDC receiving address for referral payouts, and null clears it. The only shortfall is that the expected address format (e.g., EVM 0x-prefixed) is left implicit.

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+resource ('Set the Base USDC address') and adds the purpose (receives weekly referral payouts), so an agent immediately knows what changes. It does not explicitly contrast with any sibling, though no sibling (set_dns, set_auto_renew, get_referral_stats) plausibly overlaps, so the ambiguity risk is low.

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?

Usage is implied rather than stated: an agent can infer this is the tool for directing referral payouts, and 'null to clear' signals the unset case. There is no explicit when-to-use guidance, no prerequisites (authentication, existing referral earnings), and no mention of alternatives or timing of effect.

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