Search DNS cities

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

Annotations already mark the tool readOnly, openWorld, and idempotent, so safety is covered. The description adds the workflow trait of returning selectable options, but does not disclose output shape or any pagination/edge behavior; with annotations present this 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?

Two short sentences, front-loaded with the core purpose, with the second adding the essential follow-up action. No filler and no repetition of schema details.

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 read-only two-parameter lookup with no output schema, it conveys purpose, user interaction, and the next tool to call. It could specify exactly what data is returned (e.g., city IDs for dns_set_city), but the workflow is clear enough to invoke.

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 query with an example and limit with bounds/default, so the schema carries most of the meaning. The description adds no parameter-specific detail beyond calling it a city lookup; 50% coverage is not compensated, but the undocumented limit is 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?

The description uses a specific verb ('lookup') and resource ('city'), ties it to delivery/store region, and names the follow-up sibling dns_set_city, so it is easy to distinguish from siblings like dns_get_location or dns_list_stores.

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 says to show options to the user and then call dns_set_city, which establishes when to invoke it in the city-selection workflow. It doesn't explicitly list exclusions or compare with alternative lookup tools, but the context is clear.

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