affiliate_belboon_get_earnings_summary

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

With no annotations provided, the description must carry the behavioral disclosure. It discloses that the tool returns an EarningsSummary including oldestUnpaidAgeDays and focuses on summarization, which implies a non-mutating operation. However, it does not explicitly state auth requirements, rate limits, or any side effects, leaving some uncertainty about safety and preconditions.

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, each adding value: purpose, usage context, and return/related-tool hint. Front-loaded and 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?

While the description gives a strong high-level overview and useful usage context, it omits pagination semantics (limit/cursor), the meaning of age-based filters, and any date format constraints. With 8 parameters, no annotations, and no output schema, the description is not fully complete, though it suffices for a basic selection decision.

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 adds meaning for 'date window' (from/to), 'programme' (programmeId), and 'transaction status' (status), but leaves limit, cursor, maxAgeDays, and minAgeDays unexplained. This partial coverage is inadequate for a fully self-contained tool.

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 'Summarise earnings on Belboon across a date window, with breakdowns by programme and by transaction status.' This is a specific verb+resource+scope that clearly distinguishes it from the many other network-specific earnings summary tools and from list_transactions.

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 'Use this when the user wants a single-figure answer plus context — e.g. "total earnings in Q1 with status split".' and advises 'pair with list_transactions to drill into the underlying records.' This gives clear when-to-use and alternative guidance.

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