affiliate_awin_list_commission_sharing_rules

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states that the tool returns specific data fields, which implies a read-only operation, but it does not explicitly mention authentication requirements, rate limits, or side effects. The 'raw Awin data' note adds some context, but more transparency would be needed for a full picture.

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 two sentences long and front-loaded with the primary purpose. The second sentence adds scope and return details without repetition or fluff. Every word earns its place, making it highly concise and well-structured.

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?

For a zero-parameter, read-only list tool with no output schema, the description covers the action, target account type, usage conditions, and return contents. It is fairly complete, though it could mention prerequisites like authentication or typical response size. Overall, it is sufficient for an agent to select and invoke the tool correctly.

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 accepts zero parameters, so there is no parameter ambiguity. With schema coverage of 100% (trivially, since there are no properties), the baseline is 4. The description does not need to elaborate on parameters, and it appropriately focuses on the result contents instead.

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 clearly states the action ('List') and the resource ('commission-sharing rules'), scoped to 'an Awin service partner publisher account.' It also distinguishes itself by naming a unique resource not shared by any sibling tool, and lists key return fields.

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 gives explicit guidance with 'Use this only for publishers using Awin commission sharing workflows,' which clarifies when the tool is appropriate. However, it does not name alternative tools or explicitly state when not to use it beyond this workflow restriction.

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