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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful access context ('VIP required') and a return-size cap ('up to 12'), but does not explain what 'aggregate visa outcomes' contains or how the limit affects behavior when omitted.

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 short sentences, front-loaded with the core action and output scope. The VIP prerequisite is appended efficiently with 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?

For a simple read-only retrieval tool with one parameter and no output schema, the description covers the basic purpose and access requirement. It remains vague about what an invitation round or aggregated visa outcome includes, which limits an agent's ability to know whether the result answers its question.

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% for the single limit parameter. The description partially compensates by saying 'up to 12', which explains the maximum, but it does not mention the default value of 5, the minimum of 1, or exactly what the limit controls.

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 and resource: returning up to 12 published invitation rounds plus aggregate visa outcomes. It is clear enough to distinguish from sibling tools like get_occupation_invitation_cutoffs, though it does not explicitly name the difference.

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 gives an access prerequisite ('VIP required') but no guidance on when to use this tool versus alternatives such as get_occupation_invitation_cutoffs or get_latest_overview. The agent must infer the appropriate use case.

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