get_shipping_zone

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

Annotations include readOnlyHint=true, so the agent knows this is a safe read operation. The description adds no extra behavioral context beyond what annotations provide, which is acceptable for a simple get-by-ID tool.

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 exactly two sentences, with no fluff. It states the core action and provides a useful pointer for finding IDs, earning its place without unnecessary verbosity.

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?

Given the schema covers all parameters, annotations indicate read-only safety, and the tool is a straightforward get-by-ID, the description is sufficiently complete. The 'fields' parameter is documented in the schema, and the pointer to list_shipping_zones fills the main usage gap.

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 100% with both parameters (id and fields) clearly described with types and defaults. The description does not add parameter-level details, but the schema already handles this, so the baseline of 3 is appropriate.

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 'Get a shipping zone by ID', which is a specific verb and resource. It also distinguishes from sibling tools by pointing to list_shipping_zones for ID discovery, making the purpose unmistakable.

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 second sentence 'Use list_shipping_zones to find zone IDs' provides explicit context for when to use the list tool versus this one. It implies this tool is for when you already have an ID, but does not give explicit exclusions or alternative conditions.

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