segnals_create_bot

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

With no annotations, the description fully carries the burden. It discloses that the bot starts in 'stopped' state, requires confirmation, and warns about API keys. It could mention the return value of preview/execution for full transparency.

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 (5 sentences) with each sentence serving a distinct purpose: action+scope, confirmation flow, bot state, important note. No fluff, well-structured.

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 should explain what the preview or execution returns. It lacks that, so the agent doesn't know what to expect from the tool. The exchange enum is covered by schema, but output info is missing.

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% (both parameters have descriptions). The description adds context about the confirm parameter's two-step flow but doesn't add new semantics beyond the schema. Baseline of 3 is appropriate.

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 'Create a new trading bot on Segnals.' The verb 'create' is specific and distinct from sibling tools like 'list_bots', 'get_bot', 'update_bot', etc., making the purpose unambiguous.

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 explicit guidance: requires scope 'write:bots', two-step confirmation process, and a warning about API keys. It implies when to use (to create a bot) but doesn't explicitly state when not to use or compare with alternatives, so slightly below perfect.

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