Create Production Order

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

The description discloses that components and operations are not set directly but come from BOM/routing explosion, which is behavior beyond annotations. Annotations already indicate destructiveness. No contradictions. Additional detail on external numbering also adds transparency.

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 extremely concise and front-loaded: first sentence states the action and required fields, second sentence clarifies limitations, third covers a specific parameter case. No wasted words, earning a top score.

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 has 8 parameters, 4 required, and no output schema, the description covers the required fields and a key behavioral note (BOM explosion). However, it lacks information on return values, error conditions, or post-creation behavior, which leaves some gaps for an agent relying on description alone.

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?

The schema has 100% coverage, so baseline is 3. The description adds meaning by explaining that manufacturingOrder is only for external numbering, which clarifies usage beyond the schema. This extra semantic information justifies a 4.

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 tool's purpose: creating a production/manufacturing order. It lists required fields and distinguishes itself from siblings by noting that components and operations come from BOM/routing explosion, not directly set here. This differentiation is evident when compared to sibling tools like update or release.

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 context on when to use the tool (to create an order) and notes a special case for external numbering. However, it does not explicitly state when not to use this tool or name alternative tools among the siblings (e.g., using update for existing orders). Clear context but missing exclusions.

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