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

The description goes beyond the readOnlyHint annotation by explaining how raw ticker resolution works, especially the collision between US equity tickers and crypto coins, and how to force the equity path with qualifiers. This is valuable behavioral context that annotations alone do not provide.

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?

Three dense sentences, front-loaded with the main action and return values, followed by a crucial ambiguity-resolving example. No wasted words and the structure leads with the most important 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?

Given the exhaustive input schema, output schema presence, and readOnlyHint/disructiveHint annotations, the description covers the essential call-level details including the main edge case (ticker/crypto collisions) and how to handle it. Nothing critical is missing for an agent to invoke this correctly.

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 schema already covers both parameters and their semantics, including qualification examples for the symbol field. The description restates that it takes symbol + quantity pairs but adds little beyond what the schema provides, so the baseline of 3 applies.

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 and resource: it provides live prices for holdings and explicitly lists the returned fields (price, value, day change). It is clearly distinct from the sibling macro/indicator tools, which focus on economic data and other analyses.

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 intended use case is clear: given symbol + quantity pairs, return pricing and valuation info. It does not explicitly name alternatives or exclusions, but the sibling tools are unrelated to portfolio pricing, so the context is sufficient for an agent to select this tool.

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