get_customer_sales

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

With no annotations provided, the description carries full behavioral burden. It implies a read-only report generation, but does not disclose any side effects, authentication needs, rate limits, or data modification potential. This is insufficient for an agent to understand implications.

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?

The description is a single concise sentence (15 words), but it could be slightly expanded to include key behavioral or usage hints without losing conciseness. It is not verbose but lacks some essential information.

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?

Given the tool has nested parameters and no output schema, the description is insufficient. It does not mention the report's output format, pagination, or any defaults (e.g., if all customers are included when 'customer' is omitted). The agent remains uncertain about the result structure.

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 description adds no meaning beyond the input schema. The schema already provides descriptions for 'start_date', 'end_date', 'customer', 'summarize_column_by', and 'company'. The tool description does not explain how parameters interact or any constraints (e.g., date range format validity).

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 verb 'Generate' and the resource 'Customer Sales report from QuickBooks Online' and specifies the output is 'sales by customer.' This distinguishes it from sibling tools like get_profit_and_loss or get_customer_balance.

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 provides no guidance on when to use this tool versus alternatives (e.g., get_profit_and_loss, get_customer_balance). There is no mention of prerequisites, limitations, or when it is inappropriate to use.

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