create_lot

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

Without annotations, the description carries full behavioral burden. It details: requires session, transports goods, opens lot, costs CPU if through foreign Hub, auto-approves spend, returns lotId. It also mentions API validation. No contradictions; all key behaviors are disclosed.

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?

Four sentences, each adding essential information: purpose, prerequisite, process with costing, and return value. Front-loaded and no wasted words.

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 purpose, prerequisite, process, costing, auto-approval, return, and tracking. Lacks mention of error conditions or coordinate validity, but overall sufficient for a 4-param tool with no output schema.

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% with good descriptions, so baseline is 3. The description adds value by explaining the chain format (source to hub), the costing implication of foreign routes, and reinforcing that resourceId must have balance. It complements but does not drastically surpass 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 clearly states the tool creates a lot by listing units for sale at a Hub. It uses specific verbs ('List units... for sale') and resource ('resource at a Hub'), and distinguishes from sibling tools like buy_lot and cancel_lot by explaining it returns a lotId and references list_my_lots/get_lot for tracking.

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 clear usage context: requires authentication, explains the transport process and costs, and tells how to track the result. It implicitly tells when to use (creating a sell lot) but does not explicitly mention when not to use (e.g., for buying). The prerequisite (authenticate first) is explicit.

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