create_product

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

No annotations are provided, so the description must disclose behavior. It describes that the tool creates a product and lists required/optional fields, but does not mention permissions, side effects, rate limits, or success/error behavior. Additional behavioral context would improve 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 well-structured with a clear header, WORKFLOW section, and separated required/optional fields. While it is somewhat lengthy, the organization aids readability. Could be slightly more 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?

Given the existence of an output schema, the description does not need to explain return values. It covers the workflow, required vs optional fields, and complex nested structures. Missing elements include error handling and authentication requirements, but overall it is fairly complete for a creation tool.

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 input schema is generic (just a 'data' object with additionalProperties true), so the description bears full responsibility for explaining parameters. It thoroughly lists all fields with types, notes, and conditional requirements (e.g., 'total_price required if is_combo=1'). This adds significant value beyond the schema.

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 states 'Create a new product' which is a specific verb-resource pair. It clearly distinguishes from sibling tools like update_product or delete_product, and from other creation tools like create_consignment.

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 a clear workflow: 'First call list_categories + list_brands to get valid IDs.' It also distinguishes required and optional fields. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., when not to use it).

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