shangou_create_order

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

With no annotations provided, the description fully discloses the tool's behavior: it stops before payment, returns amount and screenshot, and directs to manual payment via noVNC. It also mentions a server-side limit intercepting large amounts, ensuring the agent understands the non-destructive and advisory nature.

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 Chinese sentence that efficiently conveys the main purpose, constraints, and post-action guidance. It is front-loaded with the primary action but could be slightly more concise by separating instructions. However, it remains clear and informative without excessive verbosity.

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?

Despite having no output schema and no annotations, the description sufficiently covers all aspects: the action, the required precondition (items in cart), the server-side limit, the returned data (amount, screenshot), and the manual payment method. This is complete for the tool's simple functionality.

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 schema has 100% coverage for the single 'shop' parameter, describing it as '店铺ID或URL'. The description adds crucial context: '需已在该店加购' (must have added to cart in that shop), which goes beyond the schema and provides essential preconditions for usage.

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 generates a pending payment order for delivery, explicitly instructs to stop before submitting payment, and returns amount, screenshot, and manual payment guidance. The verb '生成' (generate) and resource '待支付外卖订单' (pending order) are precise, and it distinguishes itself from sibling tools like shangou_submit_order.

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 specifies that the shop parameter requires a shop ID/URL and that items must already be in the cart. It warns about a server-side amount limit and guides users to manually pay via noVNC. Although it does not explicitly state when not to use the tool, it implies alternatives like shangou_submit_order for actual submission.

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