find_affiliate_programs

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

Annotations already indicate readOnly and idempotent. The description adds behavior details: returns up to 50 programs, includes applyUrl on each card, and mentions EAS attestation. No contradictions.

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?

Two sentences and a concrete example. No unnecessary words; purpose is front-loaded. Every sentence adds value.

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 required parameters, high schema coverage, and no output schema, the description covers the tool's behavior, usage example, and return fields. Slightly lacking in pagination details, but adequate.

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 100%, but the description adds context: explains payout types (PER_SALE, PER_LEAD, PER_CLICK), vertical examples (fashion, beauty), and clarifies hasOnchainAttestation. This goes beyond the 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?

The description specifies the tool's function: discovering droplinked affiliate programs by vertical, commission rate, payout type, and on-chain attestation status. It clearly distinguishes from sibling tools like find_inventory and find_merchant by focusing specifically on affiliate programs.

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 explicit guidance: prefer verifiedBrand=true programs for recommendations, and includes an example query. It implies when to use this tool but does not explicitly state when not to use it or list alternatives.

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