queryCoinList

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

With no annotations, the description should disclose behavioral traits. It only describes output content, not side effects, authentication requirements, or whether the 'side' parameter filters results. The behavioral impact of the tool is unclear.

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 brief and uses bullet points for readability. It front-loads the main purpose and lists expected returns efficiently, though the parameter omission is a structural gap.

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?

Despite being a simple tool, the description covers return fields and use cases adequately, but the lack of parameter explanation and output schema reduces completeness. Some important context is missing.

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 has one parameter 'side' with no description, and the tool description does not mention it at all. This leaves the agent without understanding its purpose or effect.

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 clearly states the tool queries the list of fiat and cryptocurrencies, listing specific return fields. However, it does not differentiate from the sibling tool 'CoinListQuery', which may cause confusion.

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?

Three use cases are provided, implying when to use the tool, but there is no explicit guidance on when not to use it or how it compares to alternatives like CoinListQuery.

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