get_all_symbols

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

With no annotations provided, the description carries the full behavioral disclosure burden. It explicitly states the operation is read-only, not confirm-gated, maps to a GET endpoint, and returns OctoBot's JSON body unchanged. This goes well beyond a generic tool description.

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 extremely concise and well-structured: one purpose sentence, one endpoint/source sentence, and one behavioral/return sentence. Every sentence adds distinct value with no repetition or 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 single-parameter read-only tool, the description covers the main operational aspects: purpose, endpoint, read-only safety, and response handling. It is slightly incomplete in not detailing the exchange parameter's accepted values or the exact JSON output structure, but the core usage is adequately covered.

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 only one parameter, 'exchange', with 0% description coverage. The description merely implies the parameter's role with 'for one exchange' but does not specify valid values, format, or how exchanges are identified in OctoBot. This is insufficient compensation for the missing schema documentation.

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 opens with a specific verb and resource: 'List every trading symbol/pair OctoBot knows about for one exchange.' This clearly distinguishes the tool from sibling names like get_currency_list or get_all_currencies by focusing on symbol/pair data scoped to a single exchange.

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 usage context is implied rather than explicit: use it when you need all trading symbols/pairs for one exchange. However, it does not mention alternatives, exclusions, or how it differs from related listing tools such as get_all_currencies or get_exchange_details.

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