segnals_start_bot

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

No annotations provided; description discloses multi-step behavior, status transitions ('starting' → 'warming_up' → 'running'), and delays. Could be enhanced with idempotency or failure mode details.

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?

Well-structured with labeled sections (scope, confirmation, cold-start, important). Each sentence adds value with no repetition or fluff. Front-loaded with main action.

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?

Covers critical aspects: required parameters, behavior, prerequisites. Could mention edge cases (e.g., bot already running) but overall sufficient for a 2-param tool with no output schema.

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% with descriptive parameter names. Description adds value by explaining the two-step confirmation for 'confirm' and cold-start context. Baseline 3, elevated for additional context.

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 'Start a trading bot' using a specific verb and resource. It distinguishes from sibling tools like segnals_stop_bot and segnals_restart_bot.

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 explicit scope requirement, two-step confirmation process, cold-start note, and prerequisite about credentials. Lacks explicit when-not-to-use instructions but covers key usage context.

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