Test Siparişi Oluştur (Stage)

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: operates only in stage, no production impact, barcodes must be from stage, address fields use defaults if omitted, and commercial=true triggers mandatory fields. This is substantial, though it omits error handling or return details.

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 serving a distinct purpose: (1) main purpose and environment, (2) barcode source and defaults, (3) commercial invoice conditions. No fluff, front-loaded, concise.

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?

The description covers environment, barcode source, defaults, and conditional requirements, but lacks any mention of return value or output format. Given the tool's complexity (8 params, nested objects, conditional logic), this gap limits completeness, though it is adequate for basic usage.

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 75% (high), but the description adds critical context beyond schema: barcodes must belong to stage products, address/customer fields are optional with defaults, and commercial=true makes specific parameters mandatory. This adds meaning that helps correct invocation.

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 the tool creates a test order in the stage environment and does not affect production. The verb 'oluşturur' (creates) and resource 'test siparişi' (test order) are specific. While no sibling differentiation is explicitly made, the tool's purpose is uniquely clear among sibling tools, none of which create 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 implies usage when a test order in stage is needed, but does not provide when-not-to-use or alternatives. It gives parameter conditions (barcodes must be from stage, address defaults, commercial invoice requirements) but no broader guidance on when to choose this tool over others.

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