get_item_stock

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

No annotations are provided, so the description is the sole source of behavioral info. It says 'obtenir' (get), implying read-only, but does not state side effects, return format, or prerequisites. However, as a simple lookup, the basic behavior is clear.

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?

Three sentences with a list of example phrasings. The examples are somewhat repetitive but serve as intent-matching patterns. No redundant content about unrelated features.

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 covers what, when, and preferred alternative. Missing return value format and note about at least one parameter being required, but given the tool's simplicity and schema coverage, it is reasonably complete.

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 fully describes item_code and item_name with priorities, and the description adds no additional parameter semantics beyond that. Descriptions of example queries imply mapping but not explicitly.

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 'Obtenir le niveau de stock actuel d'un produit spécifique' (get current stock level for a specific product), which is a specific verb+resource+scope. It also distinguishes from the alternative get_all_stock by noting preference when the product is identified.

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?

Gives explicit example queries ('combien il reste de X', 'quel est le stock de Y') and explicitly states to prefer this tool over get_all_stock when the product is known. Lacks an explicit when-not, but provides sufficient context.

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