list_currencies

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

No annotations provided, and the description only states what data is returned. It does not disclose whether the operation is read-only (implied but not stated), how the limit parameter affects behavior, pagination, or any rate limits. Minimal behavioral insight.

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 very short (8 words), but this conciseness sacrifices critical details such as the verb, parameter explanation, and usage context. It is front-loaded but incomplete.

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?

Given the lack of output schema and annotations, the description should explain the return structure and behavior more thoroughly. It mentions fields but omits details like ordering, default limit, and whether the list is exhaustive or paginated.

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%, and the description adds no information about the limit parameter. The meaning of the parameter is left entirely to the schema type definition, which is insufficient for an agent to know its purpose or constraints.

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?

Description states what the tool returns (currencies with fields) but lacks an explicit action verb like 'list' or 'retrieve', relying on the name to imply the action. It distinguishes from siblings by specifying it returns a list of all tracked currencies, but does not clearly differentiate from similar list tools like list_stablecoins.

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 on when to use this tool versus alternatives. Does not mention prerequisites, typical use cases, or scenarios where a sibling tool like get_currency_feed would be more appropriate.

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