Place Lazada Order

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

Annotations already flag destructive behavior, but the description adds critical context beyond them: real money is spent and explicit user approval of the exact reviewed total is required. This helps the agent understand the real-world weight of the action and the need for human confirmation.

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?

Three sentences, each earning its place: the first gives the precondition, the second states the consequence, and the third gives an exclusion. It is front-loaded with the most important usage constraint and contains no filler.

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 the fully documented input schema, the output schema, and annotations, the description covers the essential operational context: when it is allowed, what is at stake, and when it must never happen. Nothing needed for correct invocation appears to be missing.

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 every parameter is already documented. The description does not add parameter-level details, but it reinforces the linkage between review_token, expected_total, and the exact approved review, which is useful contextual emphasis.

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 name and title clearly identify the action as placing a Lazada order, and the description reinforces the consequence by stating 'This spends real money.' It does not explicitly restate the verb 'place,' but the intent is unambiguous from the tool name, title, and surrounding checkout context.

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 gives explicit, actionable usage rules: use only after showing the immediately preceding review_checkout result and receiving explicit approval of that exact review. It also forbids unattended use, which is strong, unambiguous guidance for an agent deciding when to invoke the tool.

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