createDCABot

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

With no annotations, the description covers rate limit (3 qps per UID) and a specific error case (ban with code 421). However, it does not explain other potential errors, idempotency, or whether the bot is active immediately after creation.

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: purpose, parameter list, prerequisites, return value, error handling, rate limit, and agent hint. Every sentence adds value 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?

Given the tool's complexity (creation with multiple constraints), the description covers prerequisites, constraints, return values, error handling, and rate limits. It lacks explanation for two parameters (toolsDiscoveryParameter, channel) but otherwise is complete.

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 coverage is 0%, but the description adds meaning for frequency_in_second (common values), pairs (per-round investment amount), and mentions optional max_invest_amount. It does not explain toolsDiscoveryParameter or channel, but those may be internal.

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 verb 'Creates a DCA bot' and specifies the resource '(bot) that automatically invests at regular intervals.' It distinguishes from sibling tools like closeDCABot by focusing on creation.

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?

Explicit prerequisites (authentication, KYC, valid pairs, min 10 sec frequency, max 5 pairs) are provided. It lacks explicit 'when not to use' but the constraints and sibling list imply the tool is for creation only.

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