Resolve Quai Zone

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

The annotations already establish read-only behavior (readOnlyHint=true), and the description adds meaningful context beyond that: it performs no network call, works purely via local inspection, and treats addresses as zone-bound. This informs the agent about determinism and side-effect-freedom without contradicting 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?

The description is compact and front-loaded: the core purpose and key differentiator ('no network call') appear in the first sentence, followed by a concise background explanation and a clear usage note. No redundant or filler content is present.

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 single-parameter, read-only, local parsing tool, the description covers what the tool does, why it matters, and when to use it. It does not detail the exact return shape or invalid-address handling, but the absence of an output schema makes this a minor gap rather than a blocking one.

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 already documents the single 'address' parameter with 100% coverage. The description adds value by explaining that the address encodes both zone and ledger and by giving concrete zone examples ('cyprus1, paxos2, hydra3'), which helps the agent interpret the input and understand what the output represents.

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 states a specific action ('Determine which Quai Network shard/zone a given address belongs to'), names the resource (address), and explicitly distinguishes its mode ('purely by inspecting the address (no network call)'). It also clarifies the conceptual model (location-based addressing, zone and ledger encoded in bytes), which removes ambiguity about what the tool resolves.

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 explicit guidance on when to use this tool: 'Use this before get_balance, get_transaction, or call_contract if you need to explain or confirm which part of the network an address or transaction belongs to.' It also implies a non-network, local operation, helping the agent choose it over network-dependent siblings.

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