toast_get_hourly_sales

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

There are no annotations, so the description carries the full behavioral burden. It only conveys a read-like fetch and does not disclose output shape, date interpretation, timezone behavior, or whether the optional restaurantGuid changes aggregation. No behavioral trait beyond the tool name is revealed.

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?

A single, front-loaded sentence of about ten words contains no filler and communicates the core purpose immediately. It is as compact as possible for the information it provides.

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 annotations, no output schema, and empty parameter descriptions, the description is too thin to fully support correct invocation: the agent cannot determine businessDate's expected numeric format or the semantics of restaurantGuid, and no return structure is hinted. A simple read tool still needs those basics.

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%, and the description only clarifies businessDate as the date context while adding nothing about its numeric format or about restaurantGuid. Since the description must compensate for empty schema descriptions, this is insufficient.

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 states a specific verb-resource pair ('Get sales') with a clear grouping criterion ('broken down by hour') and a date scope ('for a business date'). This distinguishes it from report siblings like toast_get_sales_summary or toast_get_item_sales_report, so an agent can understand what this tool uniquely returns.

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?

No guidance is given about when to choose this tool over alternative sales reports or about any prerequisites (e.g., restaurant authorization). The only implied context is the business date, but there is no explicit when/when-not or alternative routing.

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