affiliate_flexoffers_get_earnings_summary

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

With no annotations, the description must carry the behavioral burden. It discloses that the tool returns an EarningsSummary including oldestUnpaidAgeDays and supports breakdowns, which adds real context. However, it does not explicitly clarify read-only status, pagination behavior, or date format handling, leaving some gaps.

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 sentences, front-loaded with purpose, then a usage example, and a companion-tool pointer. Every sentence contributes meaning and there is no redundancy or 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?

For an 8-parameter tool with no output schema and no annotations, this description provides a solid starting point with usage guidance and a return-shape hint, but it is not fully complete. It lacks parameter format details, full output structure, and explicit edge-case behavior, so an agent would still need to infer several invocation details.

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%, so the description must compensate. It maps the date window to from/to and hints at status and programme breakdowns, but leaves limit, cursor, maxAgeDays, and minAgeDays completely unexplained. Date and status formats are also unspecified, making reliable invocation difficult.

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 ('Summarise'), names the resource ('earnings on FlexOffers'), and scopes it to a date window with breakdowns by programme and status. It also distinguishes itself from list_transactions by positioning this as the summary-level counterpart.

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 states when to use the tool ('when the user wants a single-figure answer plus context') and provides a concrete example. It also directs the agent to pair it with list_transactions for drill-down, effectively identifying the alternative for more granular queries.

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