affiliate_tradedoubler_get_earnings_summary

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

With no annotations, the description should carry the burden. It discloses the aggregate behavior, return type (EarningsSummary), and a specific field (oldestUnpaidAgeDays), but does not cover auth, pagination, or default date range behavior.

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?

Three sentences, front-loaded with purpose, includes a use-case quote and return hint – no redundant words.

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 tool with 8 optional params, no annotations, and no output schema, the description covers the core use case and return shape but leaves parameter semantics and default behavior under-specified.

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%; the description implicitly covers from/to (date window), programmeId (by programme), and status (by status), but says nothing about limit, cursor, maxAgeDays, minAgeDays, or their semantics.

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 states a specific verb 'Summarise' with resource 'earnings on Tradedoubler' and explicit breakdowns by programme and status, clearly distinguishing it from list_transactions and other network-specific summaries.

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?

Explicitly says 'Use this when the user wants a single-figure answer plus context' and suggests pairing with list_transactions for drill-down, providing clear usage guidance and an alternative.

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