List every HDB town we track, with the specific flat types available for each. Free - use this to discover valid town names and flat types before calling the paid get_hdb_town_stats tool.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but description clearly indicates a read-only list operation. Does not mention side effects, but none expected. Minor missing info on potential limitations.
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 efficient sentences. First sentence states functionality, second provides usage context. No 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 no parameters and output schema present, description fully covers purpose and usage. Mentions flat types which is key detail.
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?
No parameters in schema; baseline score of 4 applies. Description doesn't need to add parameter info.
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?
Clearly states it lists every HDB town with flat types available. Distinguishable from siblings (condo/landed projects, sample data, freshness).
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?
Explicitly tells when to use (discover valid town names and flat types) and names an alternative (paid get_hdb_town_stats). Also notes it's free.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: data freshness, sample data, and listings for condos, HDB towns, and landed projects. No overlap.
All tool names follow a consistent verb_noun pattern (get_*, list_*) using snake_case, making them easy to understand.
Five tools is slightly on the smaller side but appropriate for a data portal's free tier; each tool serves a specific discovery or metadata function.
The tools cover discovery and metadata but lack any actual data retrieval endpoints (e.g., stats for districts or projects), which are described as paid. This leaves agents unable to complete core property data requests.