segnals_create_strategy

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

Discloses key behaviors: two-step confirmation, orchestration of bot creation and config application, resulting bot state ('stopped'), and security warning. No annotations provided, so description carries full burden and does so well.

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?

Concise, well-structured with bullet points, front-loaded with purpose and scope. Every sentence provides essential information 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?

Despite lack of output schema, the description covers the tool's behavior, prerequisites, and warning. The output is implied (a created strategy). Sufficient for an agent to use the tool correctly.

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 baseline is 3. The description adds context about the confirm parameter's role and the config's scope, but does not significantly expand on schema descriptions. Adequate.

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?

Clearly states the tool creates a fully configured trading strategy (bot + config), distinguishing it from sibling tools like segnals_create_bot (only creates a bot) and segnals_explain_config. The verb 'create' and resource 'strategy' are specific.

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 two-step confirmation process, required scope (write:strategies), and warns about API keys. Could further clarify when to use this versus segnals_create_bot, but overall adequate guidance.

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