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

With no annotations, the description must carry the burden. It discloses that the operation is a 'show' (read-like) and adds billing cost per call, which is valuable. However, it does not mention side effects, authentication, or limits. This is adequate for a simple read, but not rich, earning a 3.

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 short and gets to the point, with two sentences. It is front-loaded with the main action and includes cost info. However, the typo 'Bing' instead of 'Billing' and the awkward '1 Credits' reduce polish, preventing a perfect score.

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?

Given the simple tool scope, the description covers the basic function and cost, but omits context about the return format, the meaning of 'V1', and prerequisites. With no output schema or annotations, the description leaves the agent guessing about expected output structure. It is adequate but not thorough, so a 3.

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?

The input schema already describes both parameters with examples, covering 100% of schema descriptions. The description does not add extra parameter information; it only references 'Passport holder Group: V1,' which is ambiguous but not a parameter explanation. Per guidelines, high schema coverage sets a baseline of 3, so this is earned.

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 uses a clear verb and resource: 'Show the visa requirements for Passport holder Group: V1.' It clearly indicates the tool reports visa requirements, but it does not differentiate from sibling tools like post_v2_visa_check. Thus it scores 4—clear but no sibling distinction.

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 provides no guidance on when to use this tool over siblings or alternatives. It only states the tool's function and billing cost. There is no mention of prerequisites, exclusions, or when not to use it, so it falls to 'no guidance' (score 2).

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