close_order_api

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

Without annotations, the description carries full burden for behavioral disclosure. It only states the action ('executes'), with no mention of side effects, required permissions, error handling, or state changes. This is insufficient for a mutation tool.

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 a single sentence, which is concise but far too short for a tool with 10 parameters and complex optional fields. It sacrifices necessary detail for brevity, resulting in under-specification.

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 the high parameter count and presence of an output schema, the description is severely incomplete. It does not explain the tool's role in a multi-step FX trading workflow, how to specify positions to close, or interpret the output.

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 only 30%, yet the description adds zero information about any parameters. It fails to explain key parameters like settle_position, execution_type, or side, leaving the agent without meaningful guidance beyond the schema.

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 explicitly states the tool executes settlement orders for GMO Coin FX, which is a specific verb and resource. While it differentiates from sibling tools (e.g., order_api for opening orders) by name and context, the phrase 'settlement order' may not be immediately clear to all users, but overall purpose is clear.

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 no guidance on when to use this tool versus alternatives, such as needing open positions or prerequisites. It does not mention any context or exclude any scenarios, leaving the agent to infer usage from surrounding tool names.

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