create_warehouse

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

With no annotations provided, the description must disclose behavioral traits but only states the creation action without mentioning side effects, required permissions, or whether any validation occurs. It offers no additional context about the mutation, such as return values or idempotency, despite the tool being a create operation.

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?

While the one-sentence description is concise, it is under-specified and merely restates the tool name in French. It does not earn its place by adding useful information, falling into the category of under-explanation rather than efficient brevity.

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?

For a create tool with 6 parameters and no output schema or annotations, the description is highly incomplete. It lacks information about required fields, expected behavior after creation, or any preconditions, making it minimally viable but with significant gaps.

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 6 parameters with 0% description coverage, and the description does not compensate by explaining any fields. It fails to clarify required parameters (ref, label) or optional ones (zip, town, etc.), leaving meaning entirely to the raw 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 'Créer un nouvel entrepôt' clearly states the tool creates a new warehouse, with a specific verb and resource. It distinguishes itself from sibling tools like list_warehouses and get_warehouse by indicating it is the create operation.

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 no guidance on when to use this tool versus alternatives. It does not mention related list/get warehouse functions, prerequisites, or scenarios where creation is appropriate, offering no more context than the tool name itself.

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