sg_hdb_prices

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

With no annotations, the description carries the full burden. It does disclose the ordering behavior ('most recent first') and filtering capabilities, but it omits details about the 'limit' parameter's behavior, potential errors, or response format. This is a partial disclosure for a read-only data 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 a single, direct sentence that front-loads the primary purpose and key features. Every word adds value; there is no redundancy or unnecessary detail.

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 absence of an output schema and annotations, the description is too sparse. It fails to mention the 'limit' parameter, what data fields the response contains, or any source limitations. An agent would be left guessing about basic behavioral expectations beyond the filters.

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?

The schema already documents town and flat_type with examples, providing 67% coverage. The description reinforces these filters but adds no new meaning and completely ignores the 'limit' parameter, which also lacks a schema description. Thus, it does not fully compensate for the coverage gap.

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 specifies the action ('Get'), the resource ('HDB resale flat prices'), and key details like ordering ('most recent first') and filters. It distinguishes itself from sibling tools such as sg_coe_prices (COE prices) and sg_myinfo_hdb (personal HDB data).

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 usage context is implied by the description: retrieve HDB resale prices with optional filters. However, it does not explicitly mention when to choose this tool over alternatives like sg_dataset_fetch or sg_dataset_search, nor does it provide any exclusion criteria.

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