bitflow_cancel_order

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

With no annotations, the description carries the full disclosure burden, and it delivers real operational facts: no API key needed, public-endpoint rate limit of 500 req/min, and mainnet-only availability. It still omits whether cancellation is irreversible, what happens to escrowed funds, and what the response looks like.

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 core cancellation semantics are front-loaded well, but the closing 'Tip: call earning_opportunities...' is an unrelated cross-sell that does not help an agent invoke this tool and dilutes focus.

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 simple one-parameter cancel operation with no output schema and no annotations, the description covers network, auth, and rate-limit context. However, it leaves the agent without return-value or failure-mode expectations, which matters for a mutation tool.

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% and the sole parameter (orderId) is documented in the schema as 'The order ID to cancel.' The description adds no syntax or format guidance beyond that, so the baseline 3 applies.

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 (cancel) and resource (Bitflow Keeper order), and adds scope: 'Cancels a pending order before execution.' This makes it easy to distinguish from bitflow_create_order and bitflow_get_order without opening any schema.

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 'before execution' implies that the tool is used on pending orders, but it never says what to do when the order is already executed, missing, or when you should first call bitflow_get_order to confirm status. There are no explicit exclusions or named alternatives.

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