affiliate_awin_list_commission_groups

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

With no annotations, the description carries the full burden. It discloses that the tool returns commission group codes, names, rate values, conditions, and raw Awin data, which is useful. However, it does not mention any auth requirements, pagination, or data scope limitations, leaving some behavioral context implicit.

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?

The description is compact (two sentences) and front-loaded with the core action and resource. It includes a use-case hint and return summary without unnecessary fluff, making it easy to parse quickly.

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?

While the tool is not complex, the absence of an output schema and annotations combined with undocumented parameters means the description must cover more ground. It explains the return structure briefly but leaves gaps around effectiveDate behavior and extraConditionsDetails, which are nontrivial for an agent to infer.

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 0%, and the description does not compensate by explaining the parameters. It only indirectly references advertiserId via 'advertiser' and does not clarify the role of effectiveDate or extraConditionsDetails, which are essential for correct invocation.

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 uses a specific verb ('List') and identifies the unique resource ('commission groups and rates') for an Awin advertiser. It clearly distinguishes this from sibling tools like list_commission_sharing_rules or list_transactions by focusing on commission group data.

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 a clear 'when to use' context: deciding which products, customer types, or tracked parts are worth promoting. It does not explicitly mention when not to use it or name alternatives, so it misses the highest bar, but the guidance is actionable.

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