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

With no annotations, the description carries the behavioral burden. It states the core behavior (portfolio valuation), the batch nature, and fiat support, but it does not disclose the return shape, behavior on unknown coins, or any failure/error semantics. This is a reasonable but not thorough disclosure.

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 short sentences with no filler: the purpose and input format are front-loaded, and the example-like payload is more informative than longer prose would be. Every clause earns its place.

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 two-parameter tool with no output schema or annotations, the description gives enough to construct a basic call. It falls short on clarifying what the result looks like (total value vs per-coin breakdown, currency symbol) and edge cases like unsupported coins, so an agent may need to infer the output contract.

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%, but the description partially compensates by showing the exact holdings shape as [{coin, amount}, ...] and referencing fiat conversion. It does not name vs_currency, define the coin identifier format, or specify amount units, leaving part of the meaning to the raw 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?

The description uses a specific verb ('Value') with a clear resource ('a portfolio of holdings') and adds the distinguishing trait 'batch pricing,' which separates it from single-coin siblings like get_price or convert. The input shape is given immediately, so there is no ambiguity about what the tool does.

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 phrase 'batch pricing' implies this tool is for valuing multiple holdings at once, and 'any fiat' sets the currency context. However, it does not explicitly state when to prefer this over sibling tools such as get_price, convert, or profit_calc, nor does it mention any exclusions.

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