get_sales_metrics

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

With no annotations, the description fully bears the burden. It discloses the 24-48 hour data delay (last 2 days lack data), a critical behavioral trait. Additional implied read-only behavior and aggregation grouping add transparency.

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?

Three concise, front-loaded sentences: purpose, usage guidance, then behavioral and return info. No redundant words; each 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?

For a 5-parameter tool with no output schema, the description covers return contents (sales, units, orders), data delay, granularity, and usage context. It is fully adequate for an agent to understand input/output and when to invoke.

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% (all parameters have descriptions). The description adds usage context like 'longer date ranges' for startDate/endDate, implying a minimum range, and that interval groups by the enumerated values. This extra semantic value justifies a 4 above baseline 3.

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 'Get aggregated sales metrics' and specifies it's for longer date ranges (7+ days, etc.), distinguishing from sibling get_sales_summary. Also lists the returned metrics (total sales, unit count, order count grouped by day/week/month).

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 provides when to use ('for longer date ranges') and when not to use ('for yesterday/today sales, use get_sales_summary instead'). Also notes the 24-48 hour data delay, guiding the agent on data freshness.

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