get_native_prices

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, and "current" adds a freshness cue. But there is no disclosure of update latency, rate limits, or how chains without a price are handled, so the added behavioral context is thin.

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 with zero filler, well matched to a one-parameter lookup tool. It is efficient rather than padded, though it is arguably terse enough to leave needed detail out.

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?

For a simple read-only lookup with annotations covering safety, the description is mostly adequate, but with no output schema and zero parameter documentation an agent still lacks chain ID format, default/fan-out behavior, and the shape of the chain-keyed result.

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% for the single chainIds parameter, so the description must compensate; "keyed by chain" hints that chains drive the result set, but it never states accepted chain ID formats (string vs number) or default behavior when omitted. Partial compensation only.

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 concrete verb and resource ("Get current native token prices") and scopes it with examples (ETH, SOL, SUI, BNB) plus "keyed by chain." It does not distinguish itself from price-adjacent siblings like get_all_mid_prices or get_mark_price, so it stops short of a 5.

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 indication of when to use this versus other price tools, no prerequisites, and no note on what happens if chainIds is omitted. The agent must infer usage entirely from the name and siblings.

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