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

Annotations already cover the read-only, non-destructive, open-world profile. The description adds real value beyond that: page size (up to 100 homes) and an authentication prerequisite (Cotlet API key with access to this app). It stops short of describing rate limits or total-result behavior.

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 opening two sentences restate the same three output fields (final price, asking price, sale date) twice, which is wasted space. The constraints and auth note are front-loaded enough, but the redundancy costs it.

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 does the work of explaining return contents, and it also covers pagination size and the API-key prerequisite for this open-world read tool. Nothing critical is missing for correct invocation.

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 five parameters, giving a baseline of 3. The description points at the main filters (sold_since, housing type, rooms) and the 100-per-page limit, but adds no syntax or format detail 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) and resource (sold homes / slutpriser) and enumerates what is returned: final price, asking price, and sale date. This implicitly distinguishes it from active-listing siblings like hemnet_search_listings, but does not name any alternative explicitly.

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?

"Narrow it with sold_since, housing type and rooms" gives refinement context, but there is no explicit when-to-use vs when-not, nor any reference to sibling search tools (e.g. search_listings for active homes). Usage is implied rather than routed.

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