roamzy_referral

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

The description adds substantial behavioral context beyond the readOnlyHint/idempotentHint annotations: the 20% commission structure, forever duration, compounding referral chains, USDT accrual, spending on eSIM traffic, withdrawal identity requirement, and anonymous mode. These details give the agent a full understanding of the tool's behavior and constraints.

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 description is a dense paragraph but front-loads the core purpose. Each sentence contributes new information (commission, sharing, earnings, withdrawal, anonymous mode, returns). While longer than a two-sentence ideal, the complexity of the referral program justifies the length. No redundant or filler content.

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?

The description covers the tool's purpose, usage, return fields, earning mechanics, withdrawal requirements, and anonymous mode. It also explains the meaning of can_withdraw. With an output schema present and annotations providing safety hints, this description is fully complete for an agent to 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?

The input schema has zero parameters and schema coverage is vacuously 100%, so the baseline is 4. The description usefully explains return values (e.g., can_withdraw, balance_usdt) which adds semantic meaning, but no parameter clarification is needed since there are no parameters.

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 explicitly states the tool's function with a specific verb+resource: 'Get YOUR Roamzy referral link + earnings.' It clearly differentiates from sibling tools like roamzy_status or roamzy_me by focusing on referral and earnings, and enumerates the return fields.

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 provides clear guidance on when to use the tool: 'Share referral_link whenever you recommend Roamzy to ANYONE.' It gives context for both human users and AI agents, but does not explicitly state when not to use it or name alternative tools for exclusion.

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