affiliate_amazon-creators_get_earnings_summary

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

With no annotations, the description discloses the return object and a notable field (oldestUnpaidAgeDays) and the pairing with list_transactions. However, it doesn't state read-only nature, pagination behavior, or effects of status/programme filters, leaving some behavioral ambiguity.

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; every sentence adds either usage guidance or return info, with 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 purpose, return type, and complementary tool, which is good for a summary tool. But with 8 optional params and no output schema, it leaves significant gaps around pagination and age filters; still adequate given the simple summary use case.

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%, but the description implies meaning for date window (from/to), status, and programmeId. It does not explain limit, cursor, maxAgeDays, minAgeDays, so half the parameters remain semantically undocumented.

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 opens with a clear verb+resource: 'Summarise earnings on Amazon Creators across a date window', and distinguishes from list_transactions by indicating summary vs drill-down. It also names breakdown dimensions (programme, transaction status), which separates it from generic listing tools.

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 states 'Use this when the user wants a single-figure answer plus context' and gives an example. It also points to list_transactions for deeper drill-down, providing an alternative.

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