get_asset_price

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

Annotations already declare readOnlyHint=true, which covers the safety profile. The description adds useful behavioral context by specifying the returned data (previous close, percent change, session open) and implies the tool provides both price and market state, going beyond just the annotation.

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?

The description is a single, well-structured sentence that front-loads the core action ('Get the current trade price') followed by a concise list of additional data. No unnecessary words or redundant 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?

For a simple read-only tool with one required parameter, the description is fairly complete. It names the key return fields, though it does not provide an exhaustive output format or mention error cases like inactive symbols. Given no output schema exists, the description partially compensates by listing primary data points.

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?

The input schema fully describes both parameters (symbol and currency) with detailed explanations, achieving 100% coverage. The description itself adds no additional parameter semantics, so the baseline of 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?

The description clearly states the verb ('Get'), the resource ('current trade price for a symbol'), and the specific data points included (previous close, percent change, market session open). This distinguishes it from siblings like get_technicals and get_chart, which focus on different data sets.

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?

The description implies usage for fetching current price data but does not explicitly mention when to use this tool over alternatives like get_asset_info or get_chart. There are no exclusions or alternative recommendations, though the purpose itself makes the use case obvious.

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