Get DNS session city

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

The annotations already mark the operation read-only and idempotent; the description adds useful behavioral context: the value comes from the current_path cookie, anonymous sessions default to Moscow, and the result influences prices and availability. There is no contradiction with 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?

Three short sentences with the main fact front-loaded, followed by the source, default, and practical impact. Every clause earns its place and there is no filler.

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 getter with no output schema, the description is complete: it states what is returned, where it comes from, what happens for anonymous users, and why the value matters. An agent has enough information to invoke it correctly and interpret the result.

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 zero properties, so the baseline for a no-parameter tool is 4. The description correctly avoids inventing parameter guidance and instead focuses on what the returned value means.

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 title supplies the verb ('Get') and resource ('DNS session city'), and the description clearly reports the current city for the browser session, including its cookie source. This distinguishes it from siblings like dns_set_city and dns_search_cities, which modify or search cities rather than return the active session city.

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 gives clear context: this is the city currently in effect for the session and it affects prices and availability, so an agent should call it before price/availability-sensitive lookups. It does not explicitly name alternatives or exclusions, but the current-session framing implies when setting or searching cities is not the goal.

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