buy

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

With no annotations, the description carries the burden of disclosure. It does warn that this places a real trade, which is critical for an execution tool. However, it does not mention prerequisites like authentication or funds, nor what happens after order placement, such as order lifecycle or cancellation.

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 short and front-loaded with the core action, and the caution about real trades is valuable. It loses a point because listing the supported order types duplicates the schema enum rather than adding new information.

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?

The schema covers all parameters, and the description explains the tool's purpose and critical risk. However, with no annotations and no output schema, it omits useful details such as return values, order confirmation, and prerequisites, leaving the description adequate but incomplete for a high-stakes execution 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%, so the baseline is 3. The description restates the order type enum but adds no new parameter semantics beyond what the schema already documents.

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 uses a specific verb and resource: 'Place a buy order on Deribit.' It also names the supported order types, which makes the tool's function immediately clear and distinguishes it from sibling tools like sell.

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 implies this tool is for buying on Deribit, but it gives no explicit when-to-use guidance, no exclusions, and no direction to alternative tools such as sell or edit_order. The warning about real trades provides context, not usage selection guidance.

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