get_sell_price

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety/external-call profile is covered. The description adds only the word 'latest', with no disclosure of price freshness, streaming vs snapshot, or auth requirements, so it contributes little beyond the structured fields.

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?

Purpose is front-loaded in the first sentence and parameter notes follow in compact Args style. No wasted sentences, though the docstring formatting is a bit verbose for the amount of information conveyed.

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?

An output schema exists, so return values need no explanation, and the read-only nature is covered by annotations. For a simple two-parameter tool it is adequately specified, but the omitted markettype default and price-freshness semantics leave meaningful gaps.

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%, so the description must carry parameter meaning, and it does provide both parameters with useful examples (BTC as cointype, USDT as markettype). It stops short of explaining the default/behavior when the optional markettype is omitted.

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 ('Get the latest sell price for a coin'), and 'sell' naturally distinguishes it from the sibling get_buy_price. However it does not differentiate itself from get_latest_coin_price or get_latest_prices, leaving the agent to guess which price tool applies.

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 when-to-use, when-not, or alternative guidance is given, despite a cluster of overlapping price siblings (get_buy_price, get_latest_coin_price, get_latest_prices, quote_sell_now). The agent gets no help choosing among them.

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