searchSearch UkraineBorder's guides for foreign travellers to Ukraine (border crossings, customs, safety, visas and war-risk travel insurance) across 10 languages. Returns matching documents with ids to fetch.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query. |
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only and non-destructive behavior. The description adds value by stating that it returns matching documents with IDs to fetch and covers 10 languages, which helps the agent understand the subsequent workflow. No contradicting behavior disclosed.
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 concise sentences convey purpose, scope, and return behavior without wasted words. The information is front-loaded and every sentence 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-parameter tool with annotations and an output schema, the description is nearly complete—it covers scope, languages, and return pattern. The only gap is lack of differentiation from the sibling tool 'search_content', but this is a minor omission.
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 the 'query' parameter 100% with a description. The tool description adds no additional parameter semantics beyond the context of the search scope, so 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 specifies a clear verb ('Search') and resource ('UkraineBorder's guides') with added scope (border crossings, customs, safety, visas, insurance) and language coverage, distinguishing it from the sibling tool 'search_content'.
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?
Usage is implied for finding Ukraine travel guides, but the description does not explicitly state when to use it vs. alternatives or provide exclusions. The sibling tool 'search_content' is not mentioned, leaving some ambiguity.
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.
Search and search_content overlap in purpose, but search covers multi-language guides while search_content targets a specific language, so they are distinguishable. Other tools like fetch, get_cluster_summary, and the insurance tools have clear distinct roles.
Some tools use a verb_noun pattern (create_draft, estimate_quote, get_cluster_summary, get_insurance_facts), while others are single verbs (fetch, search) or a different verb_noun (search_content). This inconsistency may confuse agents expecting a uniform convention.
With 7 tools, the server is well-scoped for its purpose of travel guidance and war-risk insurance. Each tool serves a distinct function without unnecessary redundancy.
The tool set covers content search and retrieval, topic summaries, insurance quoting, draft creation, and regulatory facts, covering the core workflows. Minor gaps exist around direct policy management, but the checkout link handles purchase.