submit_order

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

With no annotations, the description carries full burden. It discloses key behaviors: 'exactly once' indicates idempotency, and 'ambiguous saves are never retried' warns of non-retry on ambiguity. This adds valuable context beyond the bare action.

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 two sentences totaling 14 words, with no fluff. The first sentence front-loads the core action, and the second adds a critical constraint. Every word earns its place.

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 (1 param, output schema exists), the description covers the action, idempotency, and retry policy. However, it omits prerequisites (e.g., order must be frozen via prepare_order), what constitutes 'ambiguous saves', and the structure of the output. Complete enough for a straightforward tool but leaves gaps for a less savvy agent.

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 coverage is 0% and the description does not explain the sole parameter 'confirmation_token'. The meaning of the token (e.g., from prior step, for idempotency) is left entirely unspecified, failing to add value beyond the schema's name and type.

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 action: 'Validate then place the frozen order exactly once.' It identifies the specific resource ('frozen order') and distinguishes itself from siblings like 'prepare_order' (which prepares) and 'add_to_cart' (which builds), making the tool's unique role obvious.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The description implies use after an order is 'frozen', but does not name predecessors like 'prepare_order' or mention prerequisites such as having a confirmation token. No disclaimers or exclusion criteria are given.

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