get_dca_bot_list

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention side effects, rate limits, authentication requirements, pagination behavior, or data freshness. The 'Returns' line is generic and adds limited behavioral context.

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 well-structured with separate Args and Returns sections. It lists all 10 parameters with explanations. While somewhat lengthy, it is necessary given the lack of schema descriptions. No redundant or trivial sentences are present.

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?

The description covers parameter semantics and return type at a high level. However, it lacks details on pagination behavior (e.g., how offset/limit interact), error handling, or performance implications for large result sets. The output schema is said to exist but not shown, so the description's return summary is adequate but not exhaustive.

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?

With 0% schema coverage, the description compensates well by explaining each parameter's meaning (e.g., 'account_id: Exchange account ID (0 = all accounts)', 'limit: Maximum bots to return (1-1000)'). The StrategyType enum is defined in the schema, but other parameters rely entirely on the description for clarity.

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 retrieves a list of DCA bots with optional filtering and sorting. This directly differentiates it from sibling tools like get_dca_bot_details (single bot) and get_dca_bot_profit_data (profit data).

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 provides no guidance on when to use this tool versus alternatives. It does not mention when to use get_dca_bot_details for specific bots or any exclusions. The agent is left to infer usage from parameter names alone.

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