get_bank_branch_locations

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

With no annotations, the description carries the full burden, but 'Get information' does at least imply a non-mutating lookup. It says nothing about pagination behavior (the offset/pagesize defaults imply paged results) or how current the branch data is, leaving meaningful gaps.

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?

A single front-loaded sentence with no filler. The scope ('retail banks in Hong Kong') is stated up front and nothing is repeated from the schema.

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?

All five parameters are schema-documented and an output schema exists, so return-value explanation is unnecessary. The definition is adequate for a simple read-only lookup, with only minor omissions around pagination and data freshness.

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%, so lang, offset, district, pagesize, and bank_name are already documented in the schema. The description adds no additional meaning such as filter-matching rules or default page behavior, so the baseline 3 applies.

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 verb ('Get') and resource ('bank branch locations') and narrows scope to retail banks in Hong Kong. 'Branch' implicitly separates it from the sibling get_atm_locations, but no sibling is named explicitly, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus get_atm_locations or get_licensed_banks_historical_data, nor any mention of prerequisites or when filtering by bank_name/district is appropriate. Usage is only implied by the noun phrase 'bank branch locations'.

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