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

With no annotations provided, the description carries full burden. It discloses return values (rating, notes, restrictions) and suggests a read-only operation via 'Check', but it does not mention any side effects, dependencies, or limitations (e.g., unsupported nationalities/destinations). This is moderate transparency but lacks edge-case behavior.

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 main purpose, then details output. Every sentence adds meaning and there is zero 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?

For a simple 2-parameter tool without output schema, the description covers inputs, outputs, and even the rating color scheme. It does not explicitly address unsupported inputs or fallback behavior, which would be useful but not critical given the examples provided.

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% for both parameters, each with examples and descriptions. The tool description adds no further parameter detail beyond what the schema already provides, so the 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 explicitly states the tool checks visa accessibility rating for a specific African student nationality and destination, which is a distinct resource from sibling tools about GPA, costs, and scholarships. The verb 'Check' and specific output (rating, notes, restrictions) 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 implies usage for visa assessment queries but does not explicitly state when to use this tool over alternatives or exclude other tools. There are no competing visa tools among siblings, so context is clear but without explicit when/when-not guidance, it falls to implied usage.

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