sales

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

With no annotations, the description carries full responsibility. It discloses pagination, date format, default behavior for 'after', and output details (per-sale price, product, email domain, refund state, totals), providing useful behavioral context beyond a bare list tool.

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 concise, information-dense sentences. Every phrase adds value: pagination, date format, default behavior, and return fields are all covered without wasted words.

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 a list tool with no required parameters and an output schema, the description covers key aspects (pagination, date range, output fields). Minor ambiguity remains around 'totals' and how pagination is controlled, but overall it is sufficiently complete.

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 descriptions are absent (0% coverage), so the description must compensate. It explains 'after' semantics (defaults to today) but leaves 'before' and 'product_id' vague, offering only partial parameter clarification.

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 clearly states the tool lists sales with a specific verb ('List') and resource ('sales'), distinguishes it from sibling tools (list_products, revenue_summary) by focusing on sales records, and adds important context about pagination and date filtering.

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?

The description implies usage for retrieving sales data and provides parameter guidance (e.g., 'after' defaults to today), but it does not explicitly state when to use this tool over siblings or mention exclusions/alternatives.

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