ccxt_list_accounts

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

Beyond the readOnly, idempotent, and non-destructive annotations, the description adds valuable behavioral context: it returns only redacted metadata and guarantees secrets are never returned. This clarifies what data is exposed, which is crucial for a config-related tool.

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 a tightly worded two-sentence summary that leads with the core action and adds a critical safety guarantee. Every word contributes meaningful information with no redundancy.

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?

With no parameters and rich annotations, the description covers the key aspects: the data source (CCXT_CONFIG_PATH) and the redaction policy. It does not detail the exact metadata fields returned, but this is adequately handled given the tool's simplicity and sibling tools for deeper exchange details.

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 has zero parameters, so the schema fully covers the input surface. The description correctly focuses on output behavior rather than repeating schema details, and it adds no unnecessary parameter information.

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 lists configured CCXT accounts from CCXT_CONFIG_PATH, with a specific verb ('List') and resource ('CCXT accounts'). It is distinct from sibling tools like ccxt_list_exchanges and ccxt_describe_exchange by naming 'accounts' explicitly.

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 use for listing configured accounts but does not explicitly state when to use this tool versus alternatives like ccxt_private_read or ccxt_list_exchanges. It provides context (CCXT_CONFIG_PATH) but no direct guidance on selection or exclusions.

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