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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it includes negative and unknown results, is a public endpoint, returns English natural-language text, and preserves sources, conditions and pagination. Return format and pagination handling are not detailed further, keeping it out of the top band.

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?

Four sentences, front-loaded with the core purpose and scoping, then filter behavior, then exclusions. Every sentence carries information, though the opening sentence's stacked list of statuses/conditions/exemptions is dense and slightly harder to parse than necessary.

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?

There is no output schema, so the description bears the burden of describing returns; it does so at a high level (natural-language text, negative/unknown results included, sources and pagination preserved). Combined with full schema coverage and full annotations, an agent has enough to call it correctly, though the exact response shape remains only loosely specified.

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%, so the baseline is 3. The description adds real semantic value by stating that omitting visaSubclass returns all options, which the schema does not spell out, and by framing results as partitioned per visa stream. It does not, however, add anything for locale or occupation beyond what the schema already documents.

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?

States a specific resource and scope: occupation-level visa applicability broken down by visa stream, including statuses, mandatory assessment conditions and exemptions. It explicitly differentiates itself from nearby siblings (get_visa_fees, get_visa_processing_times) and rules out personal eligibility, so an agent can distinguish it without opening any schema.

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?

Gives clear routing: optional visaSubclass narrows results, omitting it returns all, and fees/processing times live in separate tools. It also warns that this does not establish personal eligibility. It stops short of full when/when-not guidance relative to siblings like get_occupation or get_state_nomination_occupations, but the routing context is strong.

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