transita-mcp-server

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

With no annotations, the description discloses the tool's behavior by listing the return fields and the delta summary. It does not contradict any annotations (none provided) and gives insight into the comparison output, though it doesn't mention edge cases or more detailed behavior. The description provides sufficient transparency for a simple comparison 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?

The description is a single, focused sentence that front-loads the core purpose and then specifies the return details. Every phrase earns its place, and there is no redundant or extraneous 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 a simple schema and no output schema, the description covers the return value, comparison criteria, and the delta summary. It is largely complete, though it could explicitly mention that single-visa details are handled by a sibling tool for better contextual guidance. Overall, it provides enough information for an agent to use the tool correctly.

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 only parameter, visa_ids, is not explicitly described in the description, leaving it to the agent to infer from the name and context of comparing visa pathways. While the schema provides structural constraints (array of 2-3 strings), the description does not detail how IDs are sourced or formatted. The description partially compensates by implying that the IDs correspond to the visa pathways under comparison.

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 compares 2-3 visa pathways side-by-side, with a specific verb ('compare') and resource ('visa pathways'). It also details the comparison dimensions (processing time, cost, validity, PR-pathway, delta summary), which distinguishes it from siblings that likely focus on individual visas or country overviews.

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 the intended use case: comparing multiple visa options. It clearly conveys when to use the tool (when comparing 2-3 visas) but does not explicitly mention alternatives or exclusion criteria. The context is clear enough for an agent to select it over single-visa tools like transita_visa_details.

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 full burden. It indicates a read operation through 'Get' and specifies the returned data categories, but it does not disclose any side effects, access requirements, data recency, or behavior on invalid country codes. The transparency is adequate for a simple read tool but lacks depth.

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 concise sentence that lists the tool's outputs. Every word contributes meaning, and it avoids redundancy or filler, making it easy to quickly parse.

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 single-parameter tool, the description covers the purpose, the input context, and the expected outputs. It does not explain return structures or error handling, but given the absence of an output schema, the listed data items give sufficient expectation. It could be more complete with usage examples, but it is not critically incomplete.

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 only parameter, country_code, has 0% schema description coverage, and the description does not explain its format or accepted values. It only mentions 'destination country', providing a weak link between the parameter and the tool's purpose. The agent is left to infer the correct code format, so the description fails to compensate for the schema's lack of detail.

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 the specific verb 'Get' and clearly identifies the resource as 'summary data for a destination country', enumerating concrete data points such as visa pathways, EU status, and PR timelines. This distinguishes it from sibling tools like transita_visa_details or transita_compare_visas, making the tool's 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 implies usage when a country-level overview is needed, but it does not explicitly state when to prefer this over sibling tools like transita_visa_details or transita_compare_visas. It lacks exclusion criteria or alternative references, leaving the decision to the agent's inference.

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 must convey behavior independently. It discloses that results are ranked by eligibility, includes timeline, cost, and official links, and applies a special rule for EU citizens. This goes beyond the schema and gives the agent clear expectations of output and edge-case handling, though it omits details like required fields beyond citizenship (left to the schema).

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 core action, and every sentence earns its place: the first defines the operation, the second details output and a notable behavioral nuance. No 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?

The description covers the essential return contract (ranked matches with timeline, cost, links) and an EU-specific behavior. However, with 10 parameters and no output schema, it could clarify how optional parameters are used or whether target_countries narrows the search. The absence of any discussion of edge cases (e.g., no matches) leaves minor 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%, so the description should compensate by explaining how profile parameters influence scoring. It only refers to 'user's profile' generically and does not describe any of the 10 parameters, nor how fields like age, income_usd, or target_countries affect matching. The schema itself provides enums but no narrative, leaving the agent undersupplied on parameter usage.

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: 'Score a user's profile against every visa pathway Transita supports.' This is a specific verb-resource pair with scope, and it distinguishes from siblings like compare_visas or search_by_nationality by emphasizing ranked top matches across all pathways.

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 when a user profile needs to be evaluated against all visa options, and notes EU citizens get free-movement options first. However, it does not explicitly state when to prefer this over sibling tools such as compare_visas or provide exclusions, so guidance is implied but not fully articulated.

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?

Despite no annotations, the description discloses key behavioral details: it returns different information for round-based vs continuous-intake programmes, and includes 'official source'. It adds context beyond a simple 'check status' statement, though it does not cover edge cases like invalid IDs.

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, front-loaded with the core function, and includes usage advice without redundancy. Every sentence adds value.

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 no annotations or output schema, the description adequately covers what the tool returns, how it behaves for different programme types, and when to invoke it. It is complete enough for an agent to select and call correctly.

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 only visa_id (string, no description), and schema coverage is 0%. The description references 'a single visa pathway' but does not explain what visa_id contains or where to obtain it. The parameter name is self-explanatory, but the description does not compensate for the lack of schema detail.

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: 'Check the live intake status of a single visa pathway' and specifies what it returns (open status, last selection round/cutoff, expected next, official source). It distinguishes from siblings like compare or details by focusing on live status for a single pathway.

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?

Explicitly instructs to call it 'before recommending a pathway' to avoid sending users toward closed programmes, and explains behavior for continuous-intake visas. It provides clear usage context but does not name alternative tools or explicitly say when not to use it.

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 the burden of behavioral disclosure. It provides specifics: 'Returns 4-6 destinations with the best-fit visa for each, key stats, and FAQ' and mentions graceful fallback for uncurated slugs. This gives the agent a clear expectation of the output and behavior in an edge case, which is more than minimally 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 three sentences, each with a distinct purpose: purpose, usage context, and output/edge-case behavior. It is front-loaded with the core action, no filler, and every sentence contributes 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 simple one-parameter search tool without an output schema, the description covers the main aspects: what it returns, how it behaves on uncurated data, and when to use it. It could optionally state sorting order or define 'key stats', but these are minor omissions given the tool's simplicity.

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 only defines 'nationality' as a string with no description. The tool description compensates by clarifying it means 'citizens of a given country' and references 'slug' input. This adds meaningful semantic context beyond the bare schema, especially given the 0% schema description coverage.

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.' This is a specific verb+resource combination. It also distinguishes itself from sibling tools by positioning this as the 'ideal first stop' for relocation queries, focusing on discovery rather than comparison or 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 gives clear context for when to use this tool: 'Ideal first stop for the question "Where should I move?"' This implies it is for initial exploration. It does not explicitly name alternative tools or cases where another sibling would be preferred, which is why it doesn't reach a 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, the description carries the burden of disclosure. It transparently reveals that only a free preview of the document checklist is provided and that the full multi-section checklist is behind a $49 paywall. This is valuable behavioral context beyond a simple fetch, though it does not mention error handling or authentication.

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 concise, front-loaded sentences. The first sentence enumerates the key data fields, and the second sentence adds the paid-tier limitation. Every sentence earns its place with no filler or repetition.

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 thoroughly explains what is returned, including the free-preview aspect. With no output schema, it covers return values well. It could additionally mention potential error cases or how to obtain the visa_id, but for a single-id fetch, it is largely 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 has a single required string parameter 'visa_id' with 0% description coverage. The tool description never explicitly explains what a 'visa pathway' ID is, how to obtain it, or any expected format. Because coverage is 0%, the description must compensate, and it does not.

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 'Fetch' and clearly defines the resource as 'a single visa pathway' with a detailed list of returned content (eligibility category, processing time, fees, etc.). This unambiguously distinguishes it from sibling tools like compare, match, or search.

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 full details of a single visa are needed, and it explicitly notes the paid limitation for the full checklist. However, it does not directly contrast with alternatives or state when not to use this tool, so it stops short of full explicit guidance.

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