Get proxy price quote

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

Annotations already supply readOnlyHint=true and openWorldHint=true, and the description adds the useful fact that a single call returns the full set of rental periods (1–365 days). It does not state the currency of returned values or whether prices are live/quoted vs. cached, which for an open-world pricing call would be valuable.

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 tight sentences, zero filler. The return scope is front-loaded before the input-format detail.

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?

With no output schema, the description carries the burden of describing the return value, and it does so adequately (prices keyed by all rental periods). The only noticeable gap is how currency selection affects the response, and whether the caller must supply it or gets RUB by default.

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 coverage is 50%: country is documented in the schema, and the description reinforces it with accepted formats ('RU', numeric id_country) and examples — helpful redundancy. The currency parameter is undocumented in the description, though its enum with default 'RUB' is largely self-explanatory.

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?

States a specific verb ('Returns') and resource ('mobile proxy prices for a country') plus the exact scope (all rental periods, enumerated). An agent can distinguish this pricing lookup from buy_proxy or list_residential_plans, though no sibling is named to sharpen the boundary.

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?

No when-to-use guidance, no alternates, no prerequisites. The agent is not told how this differs from list_residential_plans or find_available_geo, both of which plausibly touch pricing/location data.

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