Sales Summary

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

No annotations are provided, so the description carries the full disclosure burden. It does add real behavioral context beyond the schema by stating the time window ('last N days') and, more valuably, the exclusion rule ('Excludes cancelled/failed/refunded orders'). It omits permission needs, rate limits, and confirmation of read-only behavior.

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 tight sentences with zero filler, front-loading the returned metrics before the scoping and exclusion rules. Every sentence earns its place.

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?

An output schema exists, so the description correctly avoids explaining return structure. It covers scope, filters, and the key exclusion rule, leaving only the (read-only) safety profile and parameter defaults unstated.

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 description coverage is 0%, so the description must compensate for two undocumented parameters. 'Covers the last N days' maps clearly to 'days', and 'top selling products' loosely implies 'top_n', but it never states that 'top_n' bounds the returned product count or that both have defaults. Partial compensation only.

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+resource ('Get sales summary') and enumerates what it returns: total revenue, order count, top selling products. This is far more specific than a tautology. It doesn't explicitly differentiate from ambiguous siblings like 'dashboard' or 'get_stock_report', which keeps it short of a 5.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternative such as 'dashboard' or 'get_orders'. Usage is only implied by the tool's purpose, so an agent gets no routing help between this and other reporting-style siblings.

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