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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context about the content returned (perk categories and vendor examples) but says nothing about result volume, pagination, or ordering, so it adds only modest value beyond the annotations.

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?

It is a single front-loaded sentence with the core purpose stated first, which is good. The trailing parenthetical of vendor names (Mercor, AfterQuery, Micro1, etc.) is a long, low-signal enumeration that consumes a large share of the text for marginal routing benefit.

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 simple read-only list tool with one optional parameter, full schema coverage, and annotations carrying the safety profile, the description is adequate: it conveys what content is returned. It still leaves gaps on result size, ordering, and how the category filter changes output, which matter for an agent deciding how to call and interpret 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?

Schema description coverage is 100% and the single optional 'category' parameter already documents its accepted values (tech_jobs, tools). The description never mentions the filter or how categories map to the listed content, so it adds no meaning beyond the schema — baseline 3 applies.

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 (List) and a well-defined resource (verified B2B SaaS perks, discounts, cloud credits, remote job pipelines), with concrete examples that clarify what kind of codes are returned. It does not, however, distinguish itself from siblings like list_all_referral_codes or list_featured_referral_codes, so an agent must infer that this is the business-focused subset.

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?

There is no explicit guidance on when to pick this over list_all_referral_codes, list_featured_referral_codes, or search_referral_codes, and no stated exclusions or prerequisites. The 'B2B SaaS / business' framing only weakly implies the use case.

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