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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds genuinely new context — that results carry an observation timestamp, market state when available, and an upstream source — which warns the agent about quote staleness and provenance, but says nothing about failure modes for unknown symbols or rate limits.

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 tight sentences, front-loaded with the capability and followed by the return shape. No filler, though the asset-class enumeration is slightly redundant with the enum.

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 usefully enumerates the return fields (price fields, market state, timestamp, source), which is real value. The remaining gap is routing: a 14-sibling toolset where several tools return price-like data, and the description never says when this one is correct.

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%, and the schema's enum explanation for `type` (auto picks the larger-by-market-cap asset) is far richer than anything in the description. The description's list of asset classes merely repeats the enum values, and it adds nothing about symbol format (ticker vs coin ID vs forex pair) beyond the schema.

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 (current quote) plus the asset classes it covers, so the operation is unambiguous. It does not distinguish itself from siblings like get_asset_intraday, get_price_history, or get_market_snapshot, so an agent can't tell from the description alone which of these is the right snapshot call.

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?

"Current quote" implies a point-in-time read rather than a series, which is the main selection signal versus get_price_history. However, there is no explicit when-to-use/when-not guidance, no mention of the intraday or bulk alternatives, and no prerequisites or rate/cost notes.

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