Recherche de produits par mot-clé avec pagination
| Name | Required | Description | Default |
|---|---|---|---|
| store | No | store_id Magento (contexte tarifaire B2C/B2B) | |
| search | Yes | Terme de recherche | |
| pageSize | No | Résultats par page (max 50) | |
| currentPage | No | Numéro de page |
Changes observed during successful MCP inspections.
Input schema / properties / storeAdded value: +{
+ "description": "store_id Magento (contexte tarifaire B2C/B2B)",
+ "type": "number"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only states 'Recherche de produits par mot-clé avec pagination'. It does not disclose whether the operation is read-only, what data is returned, or any restrictions (e.g., store context, B2B/B2C pricing, pagination limits).
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?
One short sentence with no redundant wording; front-loads the core action and object.
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?
With no output schema, the description should explain what the response looks like (e.g., product list, total count, sorting) and any behavioral nuances like default pagination or store filtering. It does not, making it inadequate for a 4-parameter 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 has 100% parameter coverage with descriptions for store, search, pageSize, and currentPage. The tool description adds no additional meaning beyond what the schema already provides.
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 uses a specific verb 'Recherche' with resource 'produits' and specifies scope 'par mot-clé' (keyword) plus 'pagination', clearly distinguishing this from sibling tools like get_product or get_categories.
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 offers no guidance on when to use this tool over siblings; it does not mention alternatives or provide context for scenarios like keyword search vs category browsing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.