Hemnet sold-price market statistics

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered without contradiction. The description adds context about the data source ('recent SOLD listings') and the computed metrics, but it does not disclose additional runtime behavior such as pagination behavior, response shape, or what happens when a free-text location cannot be resolved.

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 compact and front-loaded: it opens with the core purpose and the exact statistics returned before moving to input guidance. It has no filler, though 'Read-only' mildly repeats the readOnlyHint annotation.

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?

For a 13-parameter tool with no output schema, the description supplies the key call pattern (location_ids or location), the optional filter dimensions, and the return metric set. It does not detail output structure or edge cases like both location inputs being supplied, but the schema covers most of the remaining operational details.

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 description coverage is 85%, so the schema already documents nearly all parameters in detail. The description reinforces the key choice between location_ids and location and mentions property-type/size filters, but it adds no syntax or semantic information beyond what the schema provides.

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?

States a specific operation ('Aggregate median/average statistics from recent SOLD listings') and names the resource/scope: a location with optional property-type/size filters. This clearly differentiates it from sibling tools like hemnet_search_sold and hemnet_get_sold_listing, which return individual listing records rather than aggregate market statistics.

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 description explains the core input requirement ('Provide location_ids or a free-text location') and mentions optional filters, but it never explicitly tells an agent when to choose this tool over hemnet_search_sold or when not to. Usage is implied by the aggregate-statistics framing rather than stated as a rule with exclusions.

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