crypto_quote

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'get a quote' without revealing what data is returned (e.g., price, volume, timestamp), whether it's real-time or delayed, or any rate limits or authentication needs. This is sparse and does not help the agent anticipate the tool's behavior beyond the action itself.

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 sentence that is appropriately sized for the tool's simplicity. It is front-loaded with the primary action and contains no fluff. This is a model of conciseness.

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 has no output schema, no annotations, and the description is minimal. It does not explain what constitutes a 'quote' (e.g., current price, bid/ask), nor does it clarify the difference from crypto_prices. An agent would need more context to confidently select this tool over siblings like crypto_prices.

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 provides full coverage of the ticker parameter with an example, so the description adds no new meaning. Baseline of 3 is appropriate when schema describes the parameter completely.

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 states a specific verb ('get') and resource ('cryptocurrency quote'), which is clear. It does not distinguish from the sibling tool crypto_prices, but the verb+resource is specific enough to infer the tool fetches a current quote. This is better than vague but lacks differentiation from similar siblings.

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?

No guidance is provided on when to use this tool versus alternatives like crypto_prices or crypto_quote for other asset classes. The description does not mention which scenarios call for a 'quote' versus historical prices, nor does it point to any alternative tools. This leaves the agent to infer usage context.

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