create_order

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

Annotations provide readOnlyHint=false and destructiveHint=false, but the description adds a critical non-idempotency warning ('calling twice may create duplicates'), which goes beyond the structured fields. This helps the agent understand the safe but non-idempotent nature of the operation.

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 contains repetition ('Create an order' appears twice) and an emoji line that adds little value. Though relatively short, it could be more concise and front-loaded with the core purpose.

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 high parameter complexity (nested objects, required fields) and no output schema, the description lacks guidance on response format, usage patterns, or handling of mutual exclusive fields (externalid vs externalcheckoutid). The schema covers details, but the description fails to provide a complete contextual overview.

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% with detailed field descriptions. The description adds no additional parameter semantics beyond what the schema already provides. Baseline of 3 is appropriate.

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 explicitly states 'Create an order' and 'Create a new e-commerce order resource,' with a clear verb and resource. Among siblings like 'update_order' and 'delete_order,' it uniquely identifies this tool as the creation endpoint.

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 guidance on when to use this tool versus alternatives such as 'update_order' or other create tools. The only usage hint is the idempotency warning, but it lacks explicit context for when to prefer this over sibling tools.

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