Get Transactions Totals

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

No annotations, so description bears full burden. It discloses performance characteristic (faster) and date format requirement. Does not mention authorization or side effects, but the tool is read-only aggregation. Lacks details on error handling or data scope.

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?

Two sentences: first summarizes output, second provides usage context and date format. No redundancy, every word adds value.

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?

No output schema, but description lists returned fields (orders amount, returns, etc.). Also covers date format requirement. Could mention that result is a single aggregate, but not essential. Complete for the tool's simplicity.

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 covers all 4 parameters with descriptions. Description reinforces ISO 8601 for dates but adds no new meaning beyond schema. Baseline 3 is appropriate as schema is rich.

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?

Clearly states it gets summary totals for transactions in a period, listing specific metrics (orders, returns, etc.). Distinguishes from sibling 'list_transactions' by noting it's faster and for bottom-line needs.

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 when to use over list_transactions ('when you only need the bottom line') and provides date format requirement (ISO 8601). Implicitly says not for detailed transaction listing.

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