List the countries Discava supports (ISO code, name, flag, region). Call this to discover valid country codes for the required "country" parameter.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language for the name field ("de" or "en") | |
| grouped | No | Return countries grouped by region instead of a flat list |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, indicating a safe, non-destructive read. The description adds context by specifying the output fields (ISO code, name, flag, region) and the purpose of discovering valid country codes, which is useful beyond the annotations.
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 two sentences: the first states the action and output fields, the second gives the usage purpose. It is concise, front-loaded, and contains no unnecessary 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 the tool's simplicity, the description combined with schema and annotations covers all necessary aspects: what it returns, why to use it, and parameter details. No output schema exists, but the description mentions the return fields, so the agent can expect the result.
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 covers both parameters (lang, grouped) with descriptions, so schema coverage is 100%. The description does not add parameter-specific details, but with full schema coverage the baseline of 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 clearly states the tool's purpose: 'List the countries Discava supports (ISO code, name, flag, region).' It uses a specific verb ('list') and resource ('countries'), and differentiates from sibling tools like list_categories by focusing on country data.
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 explicitly tells when to use the tool: 'Call this to discover valid country codes for the required "country" parameter.' It provides a clear usage context, though it does not mention alternatives or when not to use it. Since no direct sibling alternative exists, this is sufficient.
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 has a clearly distinct purpose: get_business retrieves full details, get_rankings returns popularity rankings, search_businesses performs filtered searches, suggest provides autocomplete, list_categories and list_countries enumerate valid options, health_check checks API status, and send_feedback reports issues. No overlap or ambiguity.
Most tools follow a verb_noun pattern (get_business, get_rankings, list_categories, list_countries, search_businesses, send_feedback). However, 'health_check' is a noun phrase and 'suggest' is a lone verb without an object, introducing minor inconsistency.
With 8 tools covering search, details, rankings, autocomplete, enumeration, health check, and feedback, the count is well-matched to the directory's scope. Each tool earns its place without redundancy.
The tool set provides a complete workflow for discovering and retrieving business information: list available categories/countries, autocomplete input, search, get rankings, fetch full details, and report issues. No critical gaps are apparent for a read-only directory.