get_price

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

With no annotations, the description must carry the transparency burden. It does disclose that the tool 'subscribes and waits for a tick', which warns the agent of a potentially blocking call. However, it does not state read-only status, required permissions, or any side effects of the subscription.

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, concise sentence that front-loads the main action and includes a brief, informative parenthetical. Every word earns its place with no redundancy.

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?

The tool lacks an output schema, so the description should explain what the tool returns and what values are acceptable for 'asset'. It does neither, making the tool incomplete for an agent to invoke correctly. The subscription/waiting detail is helpful but not sufficient for full comprehension.

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 single parameter 'asset' has no schema description (0% coverage), and the description adds no meaning beyond the property name. It does not specify required format (e.g., ticker symbol, UUID), supported asset types, or examples, leaving the agent without the necessary information to supply valid input.

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 'Get' and resource 'current live price for an asset', clearly distinguishing it from siblings like get_candles (historical) and get_asset_info (metadata). The parenthetical 'subscribes and waits for a tick' adds a unique behavioral detail that reinforces its purpose.

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 real-time price retrieval but does not explicitly state when to use this tool over alternatives. It does not mention that get_candles would be for historical data or that get_asset_info is for metadata, so guidance is only implied.

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