create_bom

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

There are no annotations, and the description gives no behavioral information. It does not disclose side effects, permission requirements, or whether this is a write operation beyond the verb 'create'. The description carries zero behavioral burden.

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 short, but this is under-specification rather than effective conciseness. It provides no useful structure or elaboration for a tool with six parameters and no annotations.

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 tool has six parameters, no output schema, and no annotations. The description offers no context about what a BOM is, how it relates to manufacturing orders, or what the response will be. It is completely inadequate for an agent to know how to invoke this tool correctly.

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 83% (5 of 6 properties have descriptions), so the baseline is 3. The description adds no parameter-level meaning, but since the schema already documents most parameters, the tool description does not need to compensate.

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 'Créer une nomenclature de fabrication' translates directly to 'Create a manufacturing BOM', which essentially restates the tool name 'create_bom' without adding detail. It does not distinguish this tool from siblings like create_manufacturing_order or list_boms.

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 usage context is provided. The description does not explain when to use this tool versus alternatives, nor does it mention prerequisites or typical scenarios. It is a single phrase with no guidance.

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