search_hdb_resale

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

Discloses data coverage (2017 onwards) and sorting (most recent). No annotations provided, so description carries the burden. Could mention rate limits or pagination but provides useful return field list.

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?

Single sentence front-loads purpose, no filler. Efficiently conveys scope, data range, sorting, and return fields.

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 output schema, description lists return fields (price, floor area, etc.). Also mentions data coverage and sorting. Could mention the limit parameter but it's standard.

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 coverage is 100%, so baseline 3. Description restates filtering by town and flat type, but schema already describes parameters well. Adds no extra parameter meaning beyond schema.

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 verb 'Search' and resource 'HDB resale flat transactions'. Specifies filtering by town and flat type, distinguishes from sibling tools like search_area and search_nearby_amenities.

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?

States when to use (search by town, optional flat type) but does not explicitly mention when not to use or alternatives. Context is clear enough for agent to differentiate from siblings.

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