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

With no annotations at all, the description carries the full behavioral burden, and it discloses very little: nothing about authentication, rate limits, whether 'current' means real-time or delayed, or what happens for an unknown symbol. The only behavioral detail is the conditional requirement on asset_class.

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 core purpose is front-loaded in the first sentence, and the argument notes are compact. The docstring-style 'Args:' block is slightly formal for a two-parameter tool but wastes little space.

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 not be explained, and both parameters are covered. For a simple lookup this is close to adequate, but the absence of any note on data freshness, error handling, or symbol coverage leaves gaps an agent may hit in practice.

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 coverage is 0%, so the description must compensate, and it largely does: it gives concrete examples for symbol (BTC, ETH, SUI, NVDA, SPY) and supplies the allowed values 'stock'/'crypto' for asset_class, which the schema lacks as an enum. It still doesn't state the exact curated-symbol list that determines when asset_class is mandatory.

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 and resource ('Get the current price for a symbol') and names the source (WickedAPI), covering both crypto and stock. It is distinguishable from siblings like wickedapi_funding_oi and wickedapi_momentum by scope, though the description never explicitly contrasts itself with them.

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 asset_class field carries an implicit usage rule ('required for symbols outside the curated list, optional otherwise'), which is genuinely helpful context. However, there is no guidance on when to prefer this tool over sibling market-data tools such as wickedapi_momentum or wickedapi_funding_oi.

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