affiliate_awin_get_creative_performance

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

With no annotations, the description carries the full burden. It discloses the return structure ('creative report rows plus the exact query and raw Awin response') and implies a read-only operation via 'Fetch'. However, it does not describe pagination, rate limits, or potential side effects, and the mention of 'raw Awin response' could imply large or messy output without warning. Some transparency, but gaps remain.

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 exactly two sentences, front-loaded with the core action and resource, then the use case, then return value. Every sentence contributes value without repetition or filler. It is efficiently structured and appropriately sized.

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?

There is no output schema, so the description must explain return values and invocation context. It gives a high-level return summary but does not explain the date range, region, or timezone parameters, nor what 'creative report rows' contain. For a 5-parameter tool with minimal schema info, important contextual details are missing, making the description inadequate for confident invocation.

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. It mentions no details about the five parameters (to, from, region, dateType, timezone), leaving the agent without any clues about their meaning, constraints, or default behavior. This is a critical gap for a tool with 5 optional params.

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 'Fetch' and a clear resource 'Awin publisher performance aggregated by creative', with concrete examples of creativity types (banners, text links, creative tags). This clearly distinguishes it from siblings like get_advertiser_performance or get_campaign_performance by focusing on the creative dimension.

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 phrase 'Use this when comparing banners, text links, and creative tags across advertisers' provides clear contextual guidance for when to select this tool. It stops short of naming alternative tools or explicit exclusions, but the context is strong and covers the primary use case.

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