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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real behavioral context beyond that: pagination size (25 per page), how to advance pages, and the required Cotlet API key with app access. It does not describe rate limits or ordering, so 4 rather than 5.

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?

Purpose is front-loaded and each sentence adds information (scope, pagination, chaining, auth). The opening fragment 'ThriveCart: Affiliates with their approval status per product' is slightly awkward but it is not wasteful.

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 no output schema, the description carries the return-shape burden and does so by naming contact details and per-product approval status, and it covers auth and pagination. Complete enough for correct invocation, though ordering and total-count behavior are unstated.

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 the baseline is 3, but the description adds genuine meaning over the schema by stating that each page holds up to 25 affiliates and that 'page' advances the listing, which is not present in the schema's 'Page number, starting at 1' text.

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 (lists) and resource (affiliates) and clarifies the scope: contact details plus per-product approval status. It also distinguishes itself from siblings by explaining that its returned affiliate_id feeds approve_affiliate and set_affiliate_commission.

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?

Gives clear downstream usage ('Use the affiliate_id of an item in approve_affiliate and set_affiliate_commission') and implies a read-listing context, but does not explicitly state when to prefer this over any alternative listing approach or state exclusions.

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