closeDCABot

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

The description discloses that the tool may fail with a 503 status if the bot is mid-cycle, and mentions the rate limit. With no annotations provided, it does not explicitly state whether the operation is irreversible or if it has destructive side effects, but the context of 'closing' implies finality.

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 concise and well-structured. It starts with the purpose, then details the required parameter, constraints, and an agent hint. Every sentence adds value without 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?

For a 2-parameter tool with no output schema, the description covers the key aspects: parameter meanings, operational constraints (closeable state, error case), rate limits, and an agent hint. It is sufficient for the agent to use the tool correctly, though it could mention what happens on success or additional error statuses.

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 significant meaning for the close_mode parameter, explaining the three modes (1,2,3) with their effects, and provides an agent hint. The bot_id parameter is not described, but it is self-explanatory as the bot's identifier. Given the schema coverage is 0% (though actually partial), the description compensates well for close_mode.

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's purpose: 'Closes a running DCA bot.' It specifies the resource (DCA bot) and action (close), distinguishing it from sibling close tools for other bot types (e.g., closeComboBot, closeGridBot).

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 clear guidance: it requires a close_mode, notes that the bot must be in a closeable state (and may fail with 503 if mid-cycle), and gives a rate limit of 3 qps. It also offers an agent hint for using close_mode=3. However, it does not explicitly compare to alternative close tools or state when not to use it.

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