create_product

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action (create a product) with no details about side effects, permissions, idempotency, or return behavior. This is insufficient for a creation tool.

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 (one short phrase), which is efficient but lacks structure. It is front-loaded with essential info but too sparse to be fully helpful.

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's complexity (10+ fields, no output schema, no annotations), the description is incomplete. It does not explain the creation process, required fields, or the relationship to stock/inventory. More context is needed for a tool with many parameters.

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 for the top-level 'body' parameter but its description is merely 'Request body', adding no meaning. The inner properties lack descriptions in the schema, and the tool description does not explain any parameters. The agent must rely solely on field names and constraints, which is inadequate.

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 un produit (catalogue stock)' clearly states the verb 'créer' and the resource 'produit', distinguishing it from sibling tools like create_client, create_invoice, etc. It adds the context 'catalogue stock' to indicate it's for stock products.

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 guidance on when to use this tool vs alternatives, such as other create tools. No prerequisites, exclusions, or context for invocation are provided. The description is too minimal to guide an agent on appropriate usage.

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