Resolve courier location IDs (city / zone / area)

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

Beyond annotations (readOnlyHint, openWorldHint), the description explains the hierarchical traversal pattern (city->zone->area via parentId) and the relationship to create_parcel. No contradictions with 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?

Two concise sentences that front-load the main purpose and immediately follow with usage guidance. Every sentence earns its place without fluff.

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 tool's simplicity (hierarchical lookup of location IDs), the description fully covers what it does, how to navigate levels, and how to use the output. No output schema needed; return values are implied.

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?

With only 33% schema description coverage, the description adds meaning by explaining the hierarchical dependency (parentId for zone/area) and providing usage context. It clarifies the enum behavior implicitly and mentions the default courier.

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 the tool fetches hierarchical location IDs (cities, zones, areas) for couriers like Pathao. It specifies the verb 'get' and the resource 'structured location IDs', distinguishing it from siblings such as list_couriers which lists couriers, and create_parcel which uses these IDs.

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 explicitly states the tool is 'For couriers that address by structured location IDs (e.g. Pathao)' and explains how to use the resulting IDs in create_parcel. While it doesn't state when not to use it, the context is clear and sufficient.

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