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

No annotations are provided, so the description carries the full burden. It does convey that this is a non-binding estimate ('estimates', 'routing URLs'), implicitly read-only, and 'real-time' — but it says nothing about quote expiry, rate limits, auth requirements, or failure modes for unsupported pairs. Useful context, but not the complete disclosure a 0-annotation tool ideally demands.

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?

Purpose is front-loaded in a single strong sentence, followed by scannable USE/DO-NOT-USE bullets. The Args block largely restates the schema, costing a little efficiency, but the examples of valid tickers earn their place.

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-value explanation is not required, and the description covers purpose, usage boundaries, and parameter meaning. The remaining gap is behavioral (rate limits, quote validity, unsupported-pair behavior), which is minor for a read-only quote tool.

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 description coverage is 0% (only bare titles), so the description must compensate, and it does: it defines from_asset/to_asset as send/receive tickers, notes case-insensitivity, and gives concrete examples. The amount default of 1.0 is already in the schema, so that sentence is redundant, but overall the semantic gap is well covered.

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 ('Calculates real-time ... swap estimates') and enumerates the concrete outputs (fees, limits, routing URLs), so an agent knows exactly what this returns. It also explicitly separates itself from the sibling list_supported_currencies, which is the one overlap risk.

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 has explicit USE-WHEN, DO-NOT-USE, and alternative-tool directives. It names the fiat exclusion (USD/EUR) and routes supported-coin questions to list_supported_currencies, leaving nothing to inference.

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

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

No annotations are provided, but this is a parameterless read-only listing tool, so the safety burden is low. The description discloses the result content and count (15 assets), which is useful, but says nothing about authentication requirements, network standards detail, or whether the list is static or dynamic. Adequate but thin for a tool with zero annotation coverage.

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?

Front-loaded purpose sentence followed by clearly labeled usage guidance. Efficient, though the 'Usage Guidelines:' header adds minor overhead for only two short lines that could have been prose.

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 is simple (no params), an output schema exists so return values need not be described, and the description routes the agent to the right sibling. Only minor gaps (no mention of auth or refresh behavior) keep it from a 5.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies no filtering inputs are available.

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 ('Returns the complete list of 15 supported blockchain assets, ticker symbols, and network standards') and even quantifies the scope. An agent can distinguish it from the sibling get_swap_quote without opening any schema.

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 gives both directions: USE WHEN a user asks which cryptocurrencies/coins/networks are available, and DO NOT USE for exchange rates or quotes, naming get_swap_quote as the alternative. Nothing is left to inference.

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