Retrieve a list of countries with their IDs and names from the hh.ru areas directory. Get country references for vacancies and resumes across Russia and CIS.
List countries (id — name) from /areas/countries.
| Name | Required | Description | Default |
|---|---|---|---|
| raw | No | Return the full raw hh.ru JSON instead of the compact id — name listing. |
Changes observed during successful MCP inspections.
v2.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the endpoint and the compact id—name output, but does not mention authentication, rate limits, or the raw=true behavior beyond what the schema already states. Adequate for a simple read-only list, but not deeply transparent.
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?
The description is a single sentence, front-loaded with the action and output format, and contains no filler or 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?
For a tool with zero required parameters and a fully documented optional parameter, the description fully covers what an agent needs to call it correctly and what the default response shape will be. No output schema is needed here.
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 100% and the raw parameter is well documented. The description adds context by clarifying the default compact listing, but does not go beyond the schema for parameter semantics. Baseline 3 is appropriate.
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 and resource: 'List countries' from '/areas/countries'. It also states the output shape ('id — name'), making it distinct from sibling tools like get_areas or get_areas_subtree.
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 intended use is implied: this is the endpoint for a flat list of countries. However, it does not explicitly discuss when to choose this over get_areas, get_areas_subtree, or suggest_areas, nor does it mention any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.