buy_order

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

With no annotations, the description does not disclose side effects, required permissions, or whether the action is irreversible. 'Fill' implies mutation but no behavioral details are given, leaving the agent unaware of constraints or consequences.

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 one sentence (7 words) and front-loads the purpose. While concise, it sacrifices necessary detail; a slightly longer description could include context without losing efficiency.

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 tool with 3 required parameters and no output schema, the description is too minimal. It fails to explain what 'fill' means (e.g., market vs limit), expected outcomes, or how it relates to order lifecycle, leaving the agent with insufficient context.

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?

The description adds no meaning beyond the parameter names. The input schema has zero coverage and no enum constraints. Parameters like 'market' and 'amount_usdb' lack format, units, or relationships, forcing the agent to guess.

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 'Fill a single order on the order book' uses a specific verb and resource, clearly distinguishing from sibling tools like 'buy_multiple_orders' (multiple orders) and 'cancel_order' (cancelling). It precisely states the action and scope.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use 'buy_multiple_orders' or 'list_order'. The description lacks any contextual prerequisites or decision criteria.

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