segnals_delete_bot

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

No annotations present, so description carries full burden. It discloses permanence, irreversibility, prerequisite (bot must be stopped), and required scope. This is thorough for a destructive operation.

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?

Three sentences, each essential: purpose and scope, two-step process, and warning. Front-loaded with the main action. No fluff.

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 no output schema, the description covers purpose, preconditions, confirmation flow, and warning. It is complete for a delete operation. Minor gap: what the preview shows, but acceptable.

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 100%, so parameters are already documented. The description adds meaning by explaining the two-step flow and that confirm defaults to false (though schema says the same). It clarifies the purpose of confirm (preview vs execute), providing extra value beyond schema.

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 action ('Permanently delete') and the resource ('trading bot'), and distinguishes from sibling tools like segnals_stop_bot (stops but does not delete) and segnals_create_bot (creates). It also specifies the required scope.

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?

Provides clear two-step confirmation process and warns that the bot must be stopped first. Explicitly tells when to use (desire to permanently remove) and implies when not (if unsure or if bot is running). Could be more explicit about alternatives (e.g., stopping vs deleting but that is clear from context).

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