Get a Hemnet sold listing by id or URL

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

Annotations already establish read-only, open-world, and idempotent behavior. The description adds useful context by enumerating the returned data: final price, asking price, price change, m², rooms, tenure, broker, and coordinates. There is no contradiction and no hidden mutation or side-effect concern.

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 two sentences, front-loaded with the operation and input form, and followed by a compact list of return fields. Every sentence earns its place with no filler or redundant explanation.

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 single-parameter, read-only lookup with no output schema, the description is complete: it states the accepted input forms and the main returned data fields. An agent has enough information to select the tool, invoke it, and understand the expected result.

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%, and the schema description already states that id is either a Hemnet sold-listing id or a full hemnet.se /salda/ URL. The tool description repeats the accepted input forms but adds no new format, validation detail, or examples 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?

The description uses a specific verb ('Fetch'), names the exact resource ('SOLD listing'), and specifies both accepted input forms (Hemnet id or /salda/ URL). The 'SOLD' qualifier clearly distinguishes this from sibling tools like hemnet_get_listing and hemnet_search_sold.

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 clearly implies this is for retrieving full detail of a single sold listing when an id or URL is already known, rather than for searching or listing multiple results. It does not explicitly name alternatives or state when not to use it, so it stops short of full top-tier guidance.

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