Get proxy price quote

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

Annotations already declare readOnlyHint=true and openWorldHint=true, establishing safety. The description adds behavioral details: returns quotes for all durations, and country accepts ISO codes or numeric IDs. This is helpful but does not cover error handling or response format, which is acceptable given the annotations.

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?

Two sentences that efficiently convey purpose, usage guidance, and parameter constraints. Every sentence earns its place with no extraneous information.

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 price-lookup tool with annotations and no output schema, the description provides adequate context: purpose, when to use, and parameter hints. It could mention output structure but is not necessary given the straightforward behavior.

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 50% (only country is described). The description reinforces the country format and adds context about durations, but does not explain the currency parameter beyond its enum values. Baseline is 3 due to moderate coverage, and the description adds marginal 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?

The description clearly states it returns price quotes for proxies in a given country across all available durations, and positions it as a pre-purchase cost check. This distinguishes it from siblings like buy_proxy, list_proxies, and get_balance, providing a specific verb-resource-scope combination.

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?

Explicitly advises using this tool before buy_proxy to inform the user about cost. While it does not list all when-not-to-use scenarios, the single sentence provides clear context for its intended use relative to its primary sibling.

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