singapore_query_hdb_resale

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds genuinely non-obvious traits: the data starts Jan-2017 and returned coverage comes from a bundled catalog that may be stale, so metadata must be fetched for current coverage.

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?

Four dense sentences, front-loaded with purpose and scope before mechanics. Slight redundancy between 'inspect dataset first' and 'fetch metadata for current coverage,' but nothing is wasteful enough to penalize heavily.

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?

With 6 optional params, nested objects, and an output schema present, the description covers what the tool does, the prerequisite discovery step, supported query mechanics, and the coverage caveat. An agent has enough to call it correctly without opening other docs.

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 only 50%, with fields, limit, and offset undocumented in the schema. The description compensates by naming exact filters, column text search, fields selection, sort, and pagination, covering every parameter at a functional level, though it adds no syntax examples beyond what the schema shows for q/sort/filters.

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 gives a specific verb and resource ('Query Resale flat prices') plus scope ('registration date from Jan-2017 onwards') and the responsible agency. It does not distinguish itself from close siblings such as query_hdb_rentals or compare_hdb_prices, 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?

It gives an actionable prerequisite: inspect dataset d_8b84... first to discover filter fields, and warns to fetch metadata for current coverage. However, it never says when to choose this over sibling tools covering HDB rentals, median rent, or price comparison, leaving that inference to the agent.

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