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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine context beyond them: the 25-symbol ceiling, the asset classes accepted, and that each quote carries its own observation time and provider (useful for judging staleness). It does not state whether prices are real-time or delayed.

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?

One front-loaded sentence: capability, capacity, supported instruments and returned fields in that order, with zero filler. The field list is long but every item is information an agent would otherwise have to discover by calling the tool.

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 by enumerating all fields plus per-quote timestamps and providers. The main omission for a quotes tool is whether pricing is real-time or delayed, and there is no error behaviour for invalid symbols.

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 100% with a single documented parameter ("1 to 25 symbols", maxLength 16, ^-prefixed indices), so the baseline is 3. The description adds marginal value by extending the asset universe to FX pairs with a EUR/USD example, which the schema does not illustrate, but no syntax or formatting detail beyond that.

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+resource ("Latest quotes") and enumerates both the supported asset classes and the exact returned fields, so an agent knows precisely what it gets. It does not name or differentiate against near-neighbours like get_stock_snapshot or get_price_history, leaving that distinction to inference.

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?

Usage is only implied: "Latest quotes" signals point-in-time retrieval as opposed to the historical data implied by get_price_history, and the 25-symbol cap hints at batch sizing. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer routing.

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