Calcule le coût de livraison d'un ou plusieurs conteneurs maritimes vers une adresse en France. Sélectionne automatiquement le dépôt le plus économique et retourne le prix réel HT et TTC.
| Name | Required | Description | Default |
|---|---|---|---|
| quantity | Yes | Nombre de conteneurs à livrer | |
| container_type | Yes | Type de conteneur : 20ft, 40ft ou 40ft_hc (High Cube) | |
| delivery_address | Yes | Adresse complète ou ville de livraison en France |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses automatic depot selection and return of HT/TTC prices. No annotations provided, so description partially covers behavioral traits. Lacks details on potential side effects, authorization needs, or completeness of price calculation.
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 sentences efficiently convey purpose and key behavior. No redundant information.
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 no output schema, description hints at return fields (HT/TTC). Parameters are simple and well-documented. Could specify address format or currency, but overall adequate for a straightforward cost calculation 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?
Schema description covers all 3 parameters (100%). Description reiterates them in context but adds no extra semantic value beyond the schema definitions. Baseline score of 3 applies.
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?
Clear verb 'calcule le coût de livraison' with specific resource 'conteneurs maritimes vers une adresse en France'. Distinct from sibling 'getContainerDimensions' which focuses on dimensions.
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 versus alternatives. Does not specify prerequisites (e.g., address format) or when not to use it. Only describes the core function.
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.
The two tools have completely distinct purposes: one calculates delivery costs, the other retrieves dimensions. No overlap.
Both use a consistent verb_noun camelCase pattern (calculate... and get...), which is clear and predictable.
Two tools is minimal but acceptable for a narrowly focused server on container delivery and dimensions. It feels somewhat thin but not unreasonable.
The tools cover the core functions implied by the server name (cost calculation and dimension lookup), but lack additional operations like listing depots or placing orders, leaving minor gaps.
