roamzy_country_detail

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

With no annotations provided, the description carries the full burden. It discloses the tool is read-only reference info and not a purchase gate, but it does not detail the output structure, whether authentication is needed, or potential side effects. It is adequate but not rich.

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 two sentences, but the second is quite long. However, every part is useful: purpose, when to call, and why not to call during purchase. It is efficient and front-loaded, earning a 4.

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 simple lookup tool with one parameter and no output schema, the description covers purpose, usage rules, and the nature of data. It could specify the output format, but it is still fairly complete and leaves no major gaps.

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 has 100% coverage for the single parameter 'country_slug.' The description adds context that the tool provides per-MB rate for that country, but does not add significant meaning beyond the schema example. Baseline 3 is appropriate.

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 clearly states the tool returns 'the per-MB rate for a specific country,' a specific verb-resource pair. It also distinguishes itself from siblings by emphasizing it is reference info, not a purchase gate, which helps differentiate from other tools like roamzy_estimate or roamzy_list_countries.

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 explicit guidance: 'Call ONLY if the user explicitly asks about price for their destination' and 'DO NOT call this during purchase.' It also clarifies that the eSIM works in all 192 countries, so the tool is purely for reference, effectively covering when and when not to use it.

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