get_all_currencies

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

With no annotations, the description carries the full burden and does it well: it explicitly states the operation is read-only, not confirm-gated, and returns OctoBot's own JSON body unchanged. It also adds provenance by referencing the OctoBot source file for confirmation.

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 compact and front-loaded with the primary purpose. The additional sentences each add useful behavioral or technical context without unnecessary filler.

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 one-parameter tool, the description covers the operation, endpoint mapping, safety behavior, confirmation requirement, and return behavior. The main missing piece is validation of the exchange parameter value, but overall the context is largely sufficient without an output schema.

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 description adds some meaning beyond the bare schema by clarifying that the 'exchange' parameter selects the single exchange whose currency list is returned. However, it does not specify accepted exchange identifiers, formats, or how to obtain them, which is a gap given 0% schema description coverage.

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 ('List'), a clear resource ('every currency OctoBot knows about'), and a scope ('for one exchange'). It also maps to a concrete endpoint, which makes the tool's purpose unambiguous and distinguishes it from exchange-wide or symbol-focused 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?

The description implies usage when an agent needs all currencies for a particular exchange, and the 'for one exchange' wording provides some context. However, it does not explicitly name alternatives or state when not to use this tool, especially relative to the similar-looking sibling get_currency_list.

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