visa_details

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only the phrase 'full curated record', conveying that this returns comprehensive detail rather than a summary; it says nothing about auth, caching, or failure behavior for unknown slugs.

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?

A single front-loaded sentence with zero waste. Nothing to trim and the key qualifier (single, curated) appears early.

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?

With an output schema to describe the return shape, a fully documented single parameter, and annotations covering safety, the description is largely sufficient. It would be stronger if it pointed at list_visa_types as the way to obtain valid visa_id values.

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 100%, and the visa_id property carries an extensive list of example slugs, so the schema carries the semantic load. The description adds nothing about the parameter beyond what the schema already documents; baseline 3 applies.

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 states a specific verb (Get) and resource (full curated record for a single UAE visa type), and the word 'single' distinguishes it from a listing tool. However, it never names list_visa_types or visa_recommend, so sibling differentiation is left to inference.

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?

Implicit usage: an agent can infer this is a detail-lookup that requires a known visa_id (as opposed to list_visa_types or visa_recommend). There is no explicit when-to-use/when-not statement or reference to the alternative tools.

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