Preview a synthetic order

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

The description adds significant behavioral context beyond the annotations: it explains that 'seeded' samples the catalog while 'simple' invents fields, and that 'seed' reproduces an exact payload. This is useful, non-obvious information that helps the agent anticipate results. No contradiction with readOnlyHint or idempotentHint.

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 three sentences, front-loaded with the core purpose, followed by concise parameter guidance. Each sentence adds necessary information without redundancy.

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 tool's simplicity, the presence of an output schema, and the annotations, the description is complete: it covers the operation's purpose, the mode behavior, and the seed parameter. No gaps remain for the agent to guess.

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?

Despite 0% schema description coverage, the description fully explains both parameters: 'mode' with its two enum values and their implications, and 'seed' for reproducing a payload. This provides meaning beyond the raw schema definitions.

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 states the specific verb 'Generate' and resource 'one order', with the key differentiator 'without sending it'. This clearly distinguishes it from sibling tools like send_orders, which actually sends orders.

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 context for when to use the tool (previewing an order before sending) and even gives guidance on which mode to choose ('seeded' should be accepted, 'simple' should be rejected). It doesn't explicitly name sibling tools or state when not to use it, but the 'without sending it' contrast implies the alternative.

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