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

Annotations already establish this as a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds the useful detail that results include partner counts and commission settings, which is genuine return-content context given there is no output schema. It stops short of mentioning pagination, ordering, or handling of inactive programs.

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?

One sentence, front-loaded with the verb and resource, with the scope qualifier and return-content note following immediately. No filler or redundancy.

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?

With zero parameters, rich annotations, and no output schema, the definition covers what the tool returns at a useful level of abstraction (programs plus partner counts and commission settings). Minor gaps remain around result size, ordering, and whether non-active programs are included, but nothing essential to calling it is missing.

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 tool takes no parameters (0 params, empty schema), so there is no parameter meaning to disambiguate and the baseline is 4. The description correctly avoids inventing filtering options that the schema does not support.

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 gives a specific verb and resource ('List all affiliate programs') plus a scope qualifier ('you own as a merchant') that separates it from discovery-style siblings like discover_affiliate_programs. It does not explicitly name the sibling it is not, so the differentiation is implied rather than stated.

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 phrase 'you own as a merchant' implies this is for a merchant enumerating their own programs, which hints at when to use it versus joining or discovering programs. There is no explicit when-not guidance and no named alternative such as list_affiliate_partnerships or get_affiliate_program.

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