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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description adds real context beyond them: page size (up to 50 homes), the next_cursor round-trip, the fields present on each item, and the Cotlet API key access requirement. This meaningfully extends what the annotations convey.

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?

Front-loads the resource and returned data, then pagination, follow-ups and auth in dense but purposeful sentences. Nearly every sentence earns its place; only the 'Hemnet:' prefix and repeated field listing are slightly redundant.

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 no output schema, the description compensates by naming the returned fields, the page size and the cursor mechanism, and by stating the API key prerequisite. Complete enough for an agent to invoke it correctly, though it doesn't describe ordering or total-count behavior.

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 100%, so the schema already documents all 8 parameters including the include_upcoming default and cursor. The description reinforces include_upcoming behavior and the cursor/next_cursor flow but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 and resource (search Hemnet homes for sale and coming to market) with the scope and the data returned (price, fee, rooms, area). It clearly distinguishes itself from sibling reads like hemnet_get_listing and hemnet_search_sold_prices by naming what it returns and routing to get_listing/save_home for follow-up.

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?

Explains when it applies ('homes for sale in an area that match your filters' plus upcoming listings unless include_upcoming is false) and explicitly names the alternatives get_listing and save_home for the returned listing_id. It lacks an explicit when-not condition, but the context is clear.

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