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

Annotations already declare the safe read profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the description needn't restate safety. It adds genuine behavioral context beyond that: what the response contains and the edge case that continuous-intake visas return an 'open' status rather than a round/cutoff. Missing only failure behavior for an invalid or unknown visa_id.

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?

Three sentences, zero padding, and the core purpose plus the actionable call-before-recommending instruction are front-loaded before the edge-case note. Every sentence supplies information the agent needs.

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?

No output schema exists, yet the description enumerates the return payload (status, last round, cutoff score, next expectation, official source), so the agent knows what to expect. For a one-parameter read-only lookup, nothing material is missing.

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% and the single visa_id parameter carries no documentation in the schema, so the description carries the burden. The phrase 'a single visa pathway' implies the ID identifies a visa pathway, but no format, example, or lookup hint is given to help the agent construct a valid value.

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 verb+resource ('Check the live intake status of a single visa pathway') and enumerates exactly what comes back: open state, last selection round, cutoff score, next expectation, official source. That scope ('single visa pathway', live intake) cleanly separates it from compare/match/search/details siblings without needing to name them.

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 an explicit call condition with a rationale: 'Call this before recommending a pathway so you never send a user toward a closed or paused programme.' Clear when-to-use context, but no named alternatives (e.g., when to prefer transita_visa_details) and no when-not-to-use exclusions.

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