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

Adds real guidance beyond the annotations: the report covers one shift only, the cash drawer section is the authoritative over/short figure, and the agent must not recompute it from other sections. Annotations are present (openWorldHint=false, destructiveHint=false) but readOnlyHint=false on a report getter is unexplained; the description neither contradicts it nor clarifies what non-read-only behavior occurs.

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?

Front-loaded with the resource and its scope, then triggering questions, then input constraint, then the interpretation caveat. No sentence is filler; each carries either scope, selection, or output-interpretation information.

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 one required parameter, no output schema, and no nested objects, the description supplies what the schema cannot: the report's section inventory (acting as a return preview), where the id comes from, and how to read the drawer result. Nothing needed to call or interpret it 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% and already says 'Session id from get_sessions', so the baseline is 3. The description still adds value by reinforcing the source and, more usefully, ruling out station ids and user ids — a common mistaken input for this family of tools.

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 resource and scope — 'the full End of Session report for ONE shift' — and enumerates the sections it contains (sales, taxes, settlement, refunds, staff sales, tips, cash drawer). The 'ONE shift' emphasis and 'never a station or a person' carve it out from the many sales/financial siblings like hub_get_sales_breakdown and hub_get_financial_summary.

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 concrete triggering questions ('does the drawer balance', 'what did that shift take') and specifies the prerequisite source, the session id from get_sessions. It stops short of naming a specific sibling alternative to use for multi-shift or aggregate reporting, so the exclusion is implicit rather than explicit.

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