transita_visa_detailsFetch full details for a single visa pathway: eligibility category, processing time, fees, validity, PR timeline, and a free preview of the document checklist (lead time, ancillary cost, first section). The full multi-section checklist is part of Transita's $9 paid action plan.
| Name | Required | Description | Default |
|---|---|---|---|
| visa_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full transparency burden. It adds meaningful behavioral context by disclosing that only a 'free preview' of the checklist is returned, while the full multi-section checklist is behind a $9 paid action plan. This prevents incorrect expectations about output completeness.
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 tight sentences front-load the core purpose and then add the key paid-tier caveat. There is no fluff, repetition, or filler. 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?
The description adequately covers returned data categories and the paid limitation. However, it omits guidance on where visa_id comes from (e.g., a sibling search/match tool) and does not describe any output format or error behavior. For a single-parameter fetch this is acceptable but not fully complete.
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 provides only a bare visa_id string with 0% description coverage. The tool description does not explain what visa_id is, what format it takes, or how to obtain it. The phrase 'single visa pathway' weakly implies visa_id identifies a pathway, but no real semantic guidance is provided.
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 opens with a specific verb and resource: 'Fetch full details for a single visa pathway.' It enumerates concrete content (eligibility category, processing time, fees, validity, PR timeline, checklist preview), which clearly distinguishes it from sibling tools like comparison, overview, and search tools.
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 through 'single visa pathway'—an agent can infer this is for a focused lookup on one visa. However, the description does not explicitly say when to prefer it over alternatives such as transita_compare_visas or how to combine it with search/match tools to obtain the visa_id.
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 query type: comparison, country-level overview, profile matching, live status, nationality-based search, and detailed visa info. Even though visa_details and programme_status both concern a single pathway, their purposes are clearly separated as static details versus live intake status.
All tools share a consistent transita_ prefix and use snake_case, but the post-prefix patterns are mixed: compare_visas and match_visas are verb_noun, while country_overview, programme_status, and visa_details are noun-based. This is a minor inconsistency that does little to impede selection.
Six tools is an appropriate scope for a visa advisory server, covering search, comparison, detail, and status-checking without redundancy. Each tool has a clear role in the user journey from initial exploration to specific pathway evaluation.
The server covers the core advisory workflow: find destinations by nationality, get country overviews, match profiles, compare pathways, fetch details, and check current intake status. A notable minor gap is the absence of a direct 'list all visas for a country' tool, but search_by_nationality and country_overview mitigate this.