affiliate_awin-advertiser_get_programme

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

With no annotations, the description carries the burden. It discloses a read-only fetch operation and states that it returns a single Programme with key fields (commission, status, advertiser URL), providing essential behavioral context. However, it doesn't mention error handling or edge cases like missing ids.

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?

Two concise, front-loaded sentences; each clause adds value: purpose, usage condition, return type, and pairing advice. No filler.

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?

The description covers the core use case and return shape but lacks explanation of the brand parameter and any error/not-found behavior. Given no output schema and no annotations, some key information is missing, though the simple read-only nature reduces the burden.

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 0%, and while the description clarifies programmeId as the network programme id, it offers no meaning for the required brand parameter, leaving the agent to guess its purpose (likely the Awin brand/account scope).

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 tool fetches a single programme on Awin (advertiser) by network programme id, using a specific verb and resource. It distinguishes from sibling get_programme tools by specifying the Awin advertiser context and mentions the return type.

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?

It explicitly tells the agent to use this when the programme id is already known, and to pair with list_programmes when discovery is needed, providing clear when-to-use and when-not-to-use guidance.

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