broker_get_asset_data

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

With no annotations, the description discloses key behaviors: returns ticker data with spread, differs from Pro Trading, and is public. Does not detail rate limits or output structure, but covers core behavioral traits beyond schema.

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 sentences plus a brief note, no extraneous text. Front-loaded with purpose, every sentence adds essential information. Highly efficient.

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 simple read tool with two parameters and no output schema, the description covers purpose, parameters, service scope, and pricing distinction. Could briefly describe return fields, but overall complete given context.

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 100% with parameter descriptions. Description adds value by providing concrete examples (BTC, ETH, DOGE, SOL) and stating default for quote_symbol, though schema already includes default. Adds context on optionality.

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?

Clearly states 'Gets comprehensive market ticker data for a cryptocurrency' with verb and resource. Distinguishes from Pro Trading and sibling tools like broker_get_asset_price and broker_get_asset_chart by specifying the service and data type.

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?

Explicitly contrasts with Pro Trading prices and marks as [PUBLIC], guiding when to use this Broker service tool. Lacks explicit alternatives or when-not scenarios, but context is clear enough for selection.

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