Create Material (Product Master)

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

Annotation destructiveHint: true contradicts the description's assertion of creating a material, which is additive, not destructive. The description provides useful context on numbering but fails to address this contradiction or disclose other behavioral traits like side effects.

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 three sentences, each carrying specific guidance. It is front-loaded with the action and followed by critical parameter instructions, with no wasted words.

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 adequately covers required fields, numbering, and extensibility via additionalFields. For a creation tool without an output schema, it provides sufficient context for invocation, though it could mention that the response includes the new material number.

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?

With 100% schema coverage, the description adds significant value beyond the schema: it clarifies which parameters are required, explains the conditional use of 'product', and instructs to use 'additionalFields' for omitted fields. This helps agents understand parameter usage beyond basic types.

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 title 'Create Material' and description 'Create a new material/product' clearly state the action and resource. It distinguishes from sibling tools like s4_material_update (update) and s4_material_list/list (retrieve), making the purpose unambiguous.

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 explicitly lists required parameters (productType, baseUnit, industrySector) and explains when to use the 'product' parameter (external numbering) and 'additionalFields' (for any other fields). It does not explicitly mention alternatives, but the sibling set includes s4_material_update, implying this is for creation only.

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