Calcule une matrice de distances et durées entre N origines et M destinations (jusqu'à 25×25), en voiture, sur le réseau France (OpenStreetMap). Sans géométrie. Plan minimum : Growth. Mention OSM ODbL obligatoire.
| Name | Required | Description | Default |
|---|---|---|---|
| origins | Yes | ||
| destinations | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It reveals that the tool computes a matrix without geometry (so no route shapes), is limited to car travel, requires a minimum plan, and mandates attribution. It does not mention read-only or mutation status, but the function is clearly a read 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?
Two short sentences convey all essential information: purpose, constraints, output details, plan requirement, and attribution. No wasted words.
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 and minimal parameter descriptions, the description covers the key aspects: what it calculates, limits, mode, network, output type, and legal requirements. It could mention that the output is a matrix of distances/durations, but that is implied by 'matrice de distances et durées'.
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 coverage is 0%, meaning the description adds no information about parameters. Though the schema itself has some descriptions in the address field, the description does not explain the origins and destinations structure or the XOR relationship. The agent would need to infer from schema alone.
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 it calculates a matrix of distances and durations between N origins and M destinations up to 25x25, for car travel on the France network. It distinguishes from sibling tools like compute_route which computes a single route.
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 gives constraints (max 25x25, car only, France, no geometry, plan requirement, OSM attribution) but does not explicitly say when to use this tool versus alternatives like compute_route. The usage context is implied but not directly stated.
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.
Each tool targets a distinct operation: search, verify, nearby lookup, company details, routing, matrix, etc. The descriptions explicitly cross-reference similar tools (e.g., 'préfère route_matrix' for bulk distances, 'préfère verify_address' for confirmation), making the boundaries clear.
Most tools follow a consistent verb_noun pattern (search_address, get_company_details, verify_address). The exception is 'route_matrix', which is a noun phrase and breaks the pattern, though it remains readable and predictable enough.
With 9 tools, the set is well-scoped within the ideal range. Each tool provides a meaningful capability without overlap or redundancy, covering address, company, routing, and locality data.
The server covers the core read-only workflows for its domain: address search/verification/nearby, company search/details, route calculation/matrix, and locality search/list. No obvious gaps or dead ends exist for a data lookup service.