get_sales_yesterday

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

With no annotations provided, the description carries the full burden. It discloses the return fields (purchases, revenue, rank) and the timezone behavior, which is valuable context. It does not discuss side effects or auth, but for a read-only sales query this is adequate.

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 sentences cover all essential information without padding. The first sentence lists the outputs, and the second clarifies the timezone detail—no 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 simple read-only query with one optional parameter and no output schema, the description is complete: it names every returned field and the timezone nuance. There is no missing behavior that the agent needs to know.

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 schema fully describes the only parameter (platform) with allowed values and default. The description adds no extra parameter semantics beyond what the schema provides, so the baseline of 3 applies.

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 specifically identifies the resource (yesterday's sales), the verb (get), and the exact outputs (purchases, revenue, rank). It clearly distinguishes from siblings like get_sales_today by the explicit 'yesterday' scope.

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 clear context by specifying the time period (yesterday) and timezone boundary, making it obvious when to use this tool. However, it does not explicitly mention alternatives or exclusions relative to sibling tools like get_sales_summary or get_sales_today.

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