List condo/apartment projects we track, optionally filtered by district. Free - use this to discover valid project names before calling the paid stats/yield tools, rather than guessing at spelling.
| Name | Required | Description | Default |
|---|---|---|---|
| district | No | Optional two-digit postal district code to filter by, e.g. "09". Omit to list every condo project tracked. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses it is free (cost-related) and used for discovery. It does not detail rate limits or auth, but the output schema handles return data structure. Adequate for a read-only listing 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?
Two sentences, no wasted words. Purpose and usage instructions are front-loaded. Every sentence adds value.
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?
Fully adequate for a tool with one optional parameter, no nested objects, and an output schema. Covers purpose, when to use, and parameter meaning.
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 covers 100% of parameters. Description adds context: parameter filters by district, and the tool's purpose is to discover valid project names to avoid spelling errors. This enhances the schema's description.
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 condo/apartment projects with optional district filtering. Distinguishes from sibling tools like list_hdb_towns and list_landed_projects by property type and mentions it's a free tool for discovering project names.
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 advises using this tool before paid stats/yield tools to find correct project names, and warns against guessing. Implicitly excludes paid tools and sibling list tools for other property types.
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.