Transita MCP

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the behavioral disclosure burden. It discloses the output behavior (returns processing time, cost, validity, PR-pathway, and a delta summary) and adds the notable trait of highlighting fastest/cheapest/most permanent options. It does not cover all possible edge cases, but for a read-only comparison tool this is reasonably 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 compact and front-loaded with the action ('Compare') and resource. Both sentences are informative, with no filler or redundancy.

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 no output schema, the description adequately covers return values (processing time, cost, validity, PR-pathway, delta summary). The single parameter is mostly explained, but the description could note that visa_ids must correspond to pre-known pathway identifiers, a minor gap.

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 0% and the only parameter is a generic array of strings. The description adds meaning by indicating these are visa pathway identifiers and constraining to 2-3, but it does not explain where the IDs come from or their expected format. Some compensation occurs, but not fully.

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 ('Compare') and resource ('visa pathways'), clearly stating it compares 2-3 side-by-side. The return value summary differentiates it from sibling tools like transita_visa_details, which likely focuses on a single visa.

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 clearly implies use when comparing 2-3 visa pathways, which is a distinct scenario from single-detail or matching tools. It does not explicitly name alternatives or exclusions, but the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden. It indicates a read-only operation ('Get') and lists the return content, adding some transparency. However, it does not disclose potential error behavior, data source, rate limits, or limitations beyond the basic scope.

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 efficient sentence, front-loaded with the action, and includes a comprehensive list of what the tool returns without any wasteful or redundant wording.

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 simple one-parameter tool and absence of output schema, the description adequately communicates the key return categories (visa pathways, EU status, cities, PR timelines). It lacks detail on response format or edge cases, but is sufficient for a starting-point overview tool.

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 country_code string with no description (0% coverage). The description adds context by saying 'for a destination country', clarifying the parameter's role. However, it does not specify the expected format (e.g., ISO code) or constraints.

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 a specific verb ('Get') and resource ('summary data for a destination country'), and enumerates the content areas (visa pathways, EU status, score dimensions, etc.). This distinguishes it from the sibling visa-specific tools like transita_compare_visas or transita_visa_details.

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 implies usage for a high-level country overview but does not explicitly mention when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. It is inferred from the sibling tool names but not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses the return format (top matches, ranking, timeline, cost, links) and a specific behavioral nuance (EU citizens get freedom-of-movement options first). It doesn't explicitly state read-only or auth requirements, but the described behavior is complete for a matching tool.

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, front-loaded with the primary action and outcome. No filler; every sentence adds value, including the EU-specific behavior.

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 complexity (10 params, no output schema), the description covers the return value and EU pattern but omits guidance on parameter usage (e.g., which optional fields matter, how citizenship interacts with target_countries). Minimum viable but with gaps.

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 0%, yet the description does not mention any of the 10 parameters (e.g., citizenship, age, goal). It only refers generically to 'profile,' leaving the agent to infer that profile fields map to the schema. This fails to compensate for the lack of in-schema descriptions.

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?

Description explicitly states the verb 'Score' and the resource 'a user's profile against every visa pathway Transita supports.' It clearly distinguishes this from siblings like 'compare_visas' or 'visa_details' by focusing on ranking all pathways for a profile.

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?

Provides clear context: use when you have a user profile and want matched visa pathways ranked by eligibility. Does not explicitly mention when not to use it or name alternatives, but the context is strong enough for a typical agent to select it appropriately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does 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 several behaviors: live status, round-based vs continuous-specific fields, expected next step, official source, and the 'open' status for continuous-intake visas. It does not mention error/edge-case behavior, but given its read-only nature, this is a solid disclosure.

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 the main purpose front-loaded and usage guidance immediately following; the final clause about continuous-intake visas adds needed behavioral detail without excess.

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 one-parameter status tool with no output schema, the description covers the core return fields (open status, cutoff, expectations, source) and usage timing. It lacks guidance on where visa_id comes from and how to handle unknown IDs, so it is 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 required visa_id string with no description (0% schema coverage), and the description does not explain the format, source, or example values for visa_id. It only implies it identifies a 'single visa pathway', leaving the agent to guess how to obtain/format the ID; sibling tools are not referenced for ID resolution.

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 'Check the live intake status of a single visa pathway', naming a specific verb and resource, and enumerates concrete outputs (open/closed, last selection round, cutoff, expected next, official source). The title and mention of 'single pathway' distinguish it from siblings like transita_compare_visas or transita_visa_details.

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 explicitly instructs 'Call this before recommending a pathway' to avoid directing users to closed programmes, giving a clear when-to-use rule. It implies round-based vs continuous-intake contexts but does not explicitly name alternative tools or list when-not-to-use conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the output structure (4-6 destinations, key stats, FAQ) and gracefully notes a fallback behavior for uncurated slugs. This is more transparent than typical descriptions, though it could go further by confirming read-only behavior or any rate limits.

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 three sentences, each earning its place. It opens with the primary action, then provides usage context, and finishes with output details and a behavioral caveat. There is no fluff or repetition, achieving a high level of conciseness.

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 there is no output schema, the description adequately describes what the tool returns (destinations, visa options, stats, FAQ). It also sets expectations for edge cases. Missing are example inputs or explicit statement of the nationality format, but for a simple one-parameter search tool, the description is sufficiently 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 the parameter name 'nationality' with no description. The description adds meaning by referring to "citizens of a given country" and mentions "slug" in the fallback context, implying the parameter takes a slug. This is helpful but does not fully specify the expected format (e.g., country name, ISO code, or slug). The description partially compensates for the 0% schema coverage, but more detail would be better.

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 function: "Show top destinations and recommended visa pathways for citizens of a given country." It also distinguishes itself by positioning as the "ideal first stop" for a broad question, which differentiates it from sibling tools like visa_details or compare_visas. The output specifics (4-6 destinations, best-fit visa, key stats, FAQ) make the purpose unambiguous.

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 provides a clear when-to-use scenario: "Ideal first stop for the question 'Where should I move?'". This gives context for when the tool is appropriate. However, it does not explicitly mention alternatives or when not to use it, which prevents a score of 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by revealing that the checklist is only a free preview and that the full multi-section checklist is part of a paid plan. It lists the specific fields returned, giving the agent a clear expectation. It does not mention error handling, rate limits, or authentication, but for a simple read-only fetch tool, this is adequate.

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, with the core purpose front-loaded in the first sentence. The second sentence adds essential context about the paid plan without redundancy. Every piece of information earns its place, and there is no filler.

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 (one parameter, no output schema, no annotations), the description is fairly complete: it lists the return fields and notes the paid limitation. It could mention the response format or authentication, but the provided detail is sufficient for the agent to understand what to expect and when to use it.

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 has one parameter (visa_id) with no description (coverage 0%). The description does not explain visa_id beyond calling it a 'single visa pathway', which implies its identity but not its format, source, or how to obtain it. Since schema coverage is zero, the description needed to compensate, and it does not meet that need.

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 function with a specific verb ('Fetch') and resource ('full details for a single visa pathway'), and enumerates the exact content delivered (eligibility, fees, etc.). This distinguishes it from sibling tools that compare, overview, match, or search, making the purpose unmistakable.

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 provides clear context for when to use the tool: when you need detailed information for one specific visa pathway. It does not explicitly mention when not to use it or name alternatives, but the phrase 'single visa pathway' implies a focused use case that differentiates it from broader comparison or search tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.