bitflow_create_order

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

With no annotations, the description carries the full burden and does disclose key traits: the order is pending and executed later by an external Keeper service, no API key is needed, and there is a 500 req/min rate limit plus mainnet-only availability. It stops short of stating who signs/broadcasts, what fees are involved, or how the resulting order is tracked.

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?

Purpose is front-loaded in the first sentence, and the operational notes are short and scannable. The 'earning_opportunities' tip is tangential to invoking this tool and slightly dilutes focus, though it costs only one line.

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 six-parameter write operation with a nested object and no output schema, the definition covers environment and rate limits but omits what the call returns (presumably an order identifier) and how to follow up via bitflow_get_order or bitflow_cancel_order. An agent can call it, but cannot complete the create-then-track loop from this description alone.

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 description coverage is 100%, so all six parameters including the nested fundingTokens map are already documented in the schema; that sets the baseline at 3. The description adds no parameter-level meaning, notably no explanation of actionType values or how minReceivedAmount interacts with autoAdjust.

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?

States a specific verb and resource ('Create an automated swap order via Bitflow Keeper') and clarifies it produces a pending order rather than executing a swap immediately. However, it never names bitflow_swap or bitflow_get_quote as the alternatives, so the distinction from the direct-swap sibling must be inferred.

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 phrase 'pending order that will be executed by the Keeper service' implies when to use this (asynchronous/automated execution versus a direct swap), and 'Bitflow is only available on mainnet' is a real constraint. But there is no explicit when-to-use/when-not guidance relative to bitflow_swap, and the trailing tip about earning_opportunities is unrelated to selecting this tool.

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