Get revenue summary

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds valuable behavior beyond that: it walks every page (pagination), is the expensive call (performance cost), sums in integer cents (exact precision), and covers only one cart (scoping). No contradiction with annotations.

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 with zero waste: the first states the purpose, the second warns about cost and optimal usage, the third covers precision and multi-account caution. Every sentence contributes unique value and is front-loaded.

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 fully carries the burden of explaining the return: revenue grouped by product, sorted highest first, exact in cents. It also addresses the expensive pagination behavior and per-account scoping, making it complete for an agent to call correctly.

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?

The input schema documents all three parameters (account, date_from, date_to) with 100% coverage, so the baseline is 3. The description reinforces the date-range usage and single-account scoping but does not add new syntax or formatting details beyond what the schema already provides.

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 exactly what the tool does: revenue for a date range, grouped by product and sorted highest first, for a single ThriveCart account. It clearly distinguishes this from sibling tools like get_transactions (transaction list) and list_products (product catalog) without ambiguity.

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 tells agents to supply a date range rather than requesting all time, because it walks every page and is the expensive call. Also instructs running per account and never adding results together, providing clear when-to-use and when-not-to-use guidance.

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