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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only adds billing information ('Billing per call: 1000 Credits') but does not disclose whether the operation is read-only, what response shape to expect, or what 'Group: V2' means.

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 includes an operationally useful billing note without unnecessary elaboration. The fragment 'Group: V2' reads awkwardly but does not add significant bulk.

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 zero-parameter tool, the description is minimally viable: it states what data is returned and mentions cost. However, it lacks any explanation of the map data format, the meaning of 'Group: V2', or what distinguishes this endpoint from the similarly named post_v2_visa_map, leaving notable gaps in context.

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?

With zero parameters and fully covered schema, the description has no parameter details to compensate for. The 0-parameter baseline of 4 is appropriate, and the description's mention of 'all passports' clarifies the scope of the invoked result.

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 specific verb ('Show') and names a clear resource ('data for map for all passports'), so the core purpose is understandable. However, 'Group: V2' is cryptic, and differentiation from sibling post_v2_visa_map is only implicit via 'all passports' rather than explicit.

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?

There is no guidance about when to use this tool versus post_v2_visa_map, post_map, or the other sibling tools. The phrase 'for all passports' weakly implies a use case, but no alternatives or exclusions are mentioned.

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