Latest Closing Prices

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

Goes well beyond the readOnlyHint annotation, disclosing settlement lag (rows can have different dates; use the Date column), the exact conditions under which change is omitted, split-limited/partial 52-week range marking, and currency behavior per listing.

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 core operation, then edge cases in descending importance. Efficient overall, though the change-omission sentence is dense and slightly unwieldy; every sentence still carries real 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 no output schema, the description carries the return-shape burden and does so: it enumerates change, volume, trailing 52-week range, the Date column, and where the currency note appears. Complete enough to call correctly.

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%, so the schema already documents the tickers array, the 25-max cap, BRK-B/BRK.B handling, and the MIC:TICKER format. The description adds only the currency-per-listing nuance, so the baseline 3 is appropriate.

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 (Get) and resource (each ticker's newest traded, settled daily close) with scope detail on currency and the MIC:TICKER variant. The closing line 'settled history, not an intraday quote' cleanly separates it from sibling price tools like GetStockPrices.

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?

Clearly frames when to use it (settled history) and when not to (intraday), which is a genuine usage boundary. It does not name a specific alternative tool, so the routing is contextual rather than explicit.

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