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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description goes beyond them by disclosing pagination mechanics (cursor round-trip) and an auth requirement (Cotlet API key with access to this app). It does not state row caps or whether a missing cursor means no more pages, keeping it short of a 5.

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 core information is front-loaded, but the first two sentences say the same thing almost word for word ('Sales Details from your Sales Reports, one line per item sold, with earnings and sales tax'), wasting a full sentence. Trimming the duplicate would make it tight.

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?

With no output schema, the description carries the return-shape burden and does so: it explains a per-item-sold line with earnings and sales tax, plus pagination and required date range. Auth needs are covered too. Only the comparison to reporting siblings is missing.

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 coverage is 100%, so all four parameters are already documented in the schema, setting the baseline at 3. The description adds only marginal meaning for cursor (pass next_cursor back) and product_id (one listing), so no boost above baseline is warranted.

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?

States a specific verb and resource (list sales from Sales Reports) and pins down granularity: 'one line per item sold, with earnings and sales tax.' This distinguishes it from aggregate siblings like get_store_stats and get_product_stats without naming them. The near-verbatim opening repetition adds no extra clarity but does not obscure the purpose.

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?

Gives two operational pointers: use product_id to narrow to one listing, and pass next_cursor back as cursor to page. It never says when to prefer this tool over get_store_stats/get_product_stats, and no exclusions or prerequisites around date ranges are stated, so usage is implied rather than specified.

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