redeem_referral

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

With no annotations provided, the description carries the full burden. It does state the primary effect (adding 500 free API calls), but it does not disclose whether redemption is one-time, whether the API key is validated, or error behavior. These are important behavioral traits for a tool that consumes codes and modifies account quota.

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 single sentence, front-loaded with the action and benefit. It is concise and contains no unnecessary words.

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 tool is simple with only two fully documented parameters, and the description explains the core behavior and outcome. However, it lacks usage guidelines and critical behavioral disclosures (e.g., one-time use, validation), which leaves some gaps for an agent deciding to invoke it.

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 already fully documents both parameters (code and api_key) with descriptions, giving 100% coverage. The description adds no additional parameter-level nuance, so baseline 3 is appropriate.

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 uses a specific verb 'redeem' and resource 'referral code', clearly stating the outcome (+500 free API calls). It distinguishes from sibling tools like create_referral, which creates codes, and enter_giveaway, which is a different promotion type.

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 clearly implies when to use the tool (when you have a referral code to redeem), but it does not explicitly provide context on alternatives or exclusions. No mention of conditions like having an active API key or that the code can only be used once.

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