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

Annotations already indicate read-only and closed-world behavior. The description adds useful context that full profiles can be large and that topics can narrow results, though it doesn't discuss rate limits or detailed return format.

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?

It is front-loaded with the main purpose and then lists key data areas efficiently. The sentence 'Pass topics to narrow it; full profiles can be large.' is useful but could be integrated more smoothly.

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 tool's complexity and lack of output schema, the description covers most major data categories and mentions size/narrowing. It could be more complete by explicitly stating default behavior when topics are omitted.

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 schema covers 50% of parameters (country is described; topics is not). The description mentions 'Pass topics to narrow it' and lists many topics, implicitly mapping to the topics parameter, but does not explain the enum values or default behavior.

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 explicitly states the tool returns comprehensive country profile data across specific domains (visas, residency, taxes, etc.), and this scope is clearly distinguishable from siblings like find_visas or check_tax_blacklists.

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 implicitly guides usage by saying 'Pass topics to narrow it' and notes that full profiles can be large, suggesting a when-to-use-case. However, it lacks explicit comparison to alternatives such as compare_countries or find_visas.

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