affiliate_awin_list_transaction_queries

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns paginated rows with specific fields (advertiser, click reference, status, amount), which is useful. However, it lacks details on authentication, default behavior with no parameters, rate limits, or how pagination works, so transparency is only moderate.

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 three concise sentences, front-loaded with the core purpose, followed by usage context and return details. Every sentence adds value with no wasted words, making it highly scannable for an agent.

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?

Despite having 9 parameters and no output schema, the description does not cover essential context such as date range requirements, default values, timezone handling, or how to filter by advertiser. It mentions return fields but omits behavioral details like whether all queries are included by default. The description is insufficient for full autonomous use.

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 adds no parameter-level semantics. It does not explain the purpose or format of to/from, dateType, statuses, or any other parameters. The description must compensate for the lack of schema descriptions but fails entirely, leaving the agent to guess parameter meanings.

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 it lists Awin transaction queries, with the scope 'raised by or visible to the publisher', distinguishing it from general transaction listing tools. It also specifies the resource (transaction queries) and provides a concrete use case, making its purpose immediately understandable.

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 explicitly says when to use this tool: 'when investigating missing, incorrect, pending, or declined transaction enquiries.' This provides clear context for selection, though it does not explicitly mention alternatives or when not to use it. The guidance is actionable and sufficient for distinguishing from sibling tools.

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