get_referral_link

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

With no annotations, description carries full burden. It states 'Free. Side effects: none' and lists return format. While sufficient, it could elaborate on auth or rate limits, but core behavioral traits are disclosed.

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?

Description is three lines: purpose, usage guidelines, and returns/side effects. No wasted words, front-loaded, and structured.

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?

Given no output schema, description provides return format. Covers purpose, usage, returns, and side effects for a simple 1-param tool. 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?

Description does not mention the parameter 'referrer', but schema coverage is 100% and schema provides a good description. Baseline 3 is appropriate as description adds no semantic value beyond schema.

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?

Description clearly states 'Generate referral URL to invite other agents to HyperNatt Terminal / NattSwap' with a specific verb and resource. It also distinguishes from sibling tool get_agent_balance via explicit 'NOT WHEN' clause.

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 provides 'USE WHEN: growth / affiliate onboarding' and 'NOT WHEN: checking rewards (get_agent_balance)', giving clear context and an alternative.

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