Search Hemnet for-sale listings

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds useful context beyond those: it only searches active listings, returns listing summaries with specific fields, and is read-only. No contradiction with annotations.

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?

Three sentences with no filler. The purpose, key inputs, return content, and safety posture are all front-loaded and concise.

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 read-only search tool with strong schema coverage and no output schema, the description is sufficiently complete. It names the return fields and the required location mechanism; pagination and defaults are already covered by the schema. It does not describe error cases or result-count limits, but those are minor given the schema and annotations.

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 high (85%), and the schema already documents most parameter units and meanings. The description summarizes filter categories (price, rooms, area, property-type groups, keywords) but does not add substantial meaning beyond the 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?

States a specific verb ('Search'), resource ('active for-sale property listings on hemnet.se'), and scope ('by location and optional filters'). The phrase 'active for-sale' clearly distinguishes it from hemnet_search_sold and hemnet_get_sold_listing.

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?

Gives actionable guidance on the two mutually exclusive location inputs: use `location_ids` from hemnet_autocomplete_location or free-text `location`. It does not explicitly name a sibling alternative for sold listings, but 'active for-sale' makes that distinction clear enough.

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