buy_lot

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

With no annotations, description fully discloses key behaviors: auto-approves spend, reserves immediately (no dry-run), payment breakdown, chain structure, rejection condition, and auto-refund on lapse. No contradictions.

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?

Description is clear and front-loaded with the action, but slightly verbose with nested details. Could be slightly more concise without losing essential 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?

Covers major aspects (payment, reservation, chain, rejections, refunds). Missing a brief mention of the return value (e.g., transport ID), but given no output schema, it's a minor gap for a complex 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 covers all parameters at 100% coverage. Description adds meaningful context beyond schema: explains chain array purpose, value as positive integer string, and lotId source. Baseline 3 increased due to added value.

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?

Description clearly states 'Buy units from an OPEN lot, delivered to your own cell.' with specific verb and resource. It distinguishes from sibling tools like quote_buy (preview) and lists related tracking tools.

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?

Explicitly advises to 'preview the exact cost first with quote_buy' and directs to use list_my_transports / get_lot for tracking. Also explains condition when a pending buy on the same lot is rejected.

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