list_affiliates

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

No annotations provided, so description must disclose behavior. It does not mention pagination, read-only nature, auth requirements, or rate limits. Only states it lists data, but lacks behavioral context beyond what schema implies.

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?

Single sentence, to the point, no wasted words. Could be slightly improved by hinting at pagination, but overall efficient.

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 should indicate response format. It mentions commission and earnings but not structure or pagination. With 3 simple params and full schema coverage, it's adequate but missing some context.

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%, so baseline is 3. Description adds no extra meaning beyond schema—parameters like 'status', 'page', 'per' are self-explanatory. No elaboration on how commission/earnings data is structured.

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 it lists affiliate partners with commission and earnings data, using specific verb 'list' and resource 'affiliate partners'. It distinguishes from siblings like 'get_affiliate' and 'get_affiliate_summary'.

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?

Implied usage is to list all affiliates, but no explicit guidance on when to use this vs alternatives like 'get_affiliate' for a single affiliate. No exclusions or prerequisites mentioned.

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