country_indexThe omelette price index by country. Without arguments: every published country ranked by price (EUR, trimmed median). With a country: that country's full reading.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | ISO 3166-1 alpha-2 country code, e.g. US, DE, SE |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the burden. It usefully discloses that prices are in EUR, use a trimmed median, only published countries appear, and the behavior changes with the optional argument. However, 'full reading' is vague about what fields, ordering, or format the response contains, and no error behavior is mentioned.
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 with no filler: the first states the resource and scope, the second explains the no-arg and with-arg behaviors. It is front-loaded and every clause earns its place.
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 one-optional-parameter lookup the description covers the main call patterns, but without an output schema it leaves 'full reading' unspecified and does not clarify response shape, sorting direction, or invalid-input behavior. It also lacks any comparison to sibling tools, which would help agents select this over cities or compare.
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 already fully documents the single country parameter with ISO alpha-2 constraints and examples. The description adds the contextual meaning that providing the country selects that country's full reading, which is helpful but does not go beyond the schema's documented purpose.
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 identifies the tool as the omelette price index by country and differentiates the two call modes: no-argument returns a ranked list of all published countries, while a country argument returns that country's full reading. It does not explicitly contrast itself with sibling tools such as cities or compare, so it stops short of full differentiation.
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?
It gives direct conditional usage guidance: invoke with no arguments for the full country ranking and with a country code for a single country's reading. It does not mention when not to use this tool or point to alternatives like compare or index_overview.
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 geographic level or analytical view, but compare and country_index can both return country-level price rankings, so an agent may need to read the descriptions carefully to choose correctly. Overall, the boundaries are clear enough for most queries.
Names are consistently lowercase snake_case and mostly noun phrases describing the returned view, but compare stands out as a standalone verb. The pattern is still readable and predictable.
Five tools is well-scoped for a focused data retrieval server. Each tool provides a distinct view—overview, countries, cities, subdivisions, and comparisons—without unnecessary redundancy.
The set covers the full read-only surface of The Omelette Index: global statistics, country rankings and details, city readings with filters, subdivisions by country, and country comparisons. There are no obvious dead ends for typical lookup workflows.