shangou_submit_order

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

Describes the exact behavior: submits order, stops at checkout without payment, returns payment link and screenshot. Discloses that the link is session-bound and must be opened in the browser. No annotation 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?

The description is somewhat dense but front-loaded with key action and essential usage guidance. Could be slightly more concise, but every sentence adds value.

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?

Given one parameter and no output schema, the description fully covers what the tool does, what it returns, and the necessary context (browser, login, amount limit). Complete enough for agent decision.

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?

Single parameter 'shop' is well described in schema as shop_id from shangou_search. The tool description repeats this without adding extra meaning. Schema coverage is 100%, so baseline 3.

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 it submits an order and stops at the Alipay checkout without paying, distinguishing it from sibling tool shangou_create_order which is for order creation and amount verification.

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 says to call only after user consent and typically after shangou_create_order for amount check. Also mentions amount limit and that the payment link requires the browser session.

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