Créer un(e) produit

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

The description discloses that the tool creates a product and returns the created product's data with ID. It aligns with annotations (readOnlyHint=false, destructiveHint=false) and adds return value context, but does not go deeper into permissions or 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?

Two short sentences, one for purpose and one for return value. No redundant information, front-loaded and efficient.

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 simple create operation, the description covers the purpose and return value. The presence of an output schema and complete parameter descriptions makes this sufficient, though it could mention typical validation or duplicate handling.

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 describes all six parameters with 100% coverage, so the description doesn't need to add parameter details. It adds no additional semantic 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 clearly states the action (create) and the resource (product) within BoondManager, using a specific verb and noun. It distinguishes from sibling product tools (search/get/update/delete) by the create verb.

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 clearly implies this is the tool for creating a product. However, it does not explicitly mention when not to use it or reference alternatives like update or delete, so it lacks explicit exclusion guidance.

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