Search Blocket

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

With no annotations, the description carries full responsibility for behavioral disclosure. It honestly reveals a non-obvious limitation: the location filter is by region (län) rather than a precise km radius, and it states what each result contains (coordinates/distance) so the agent can apply its own precise filtering. This is high-value transparency beyond the schema.

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 four sentences, each adding distinct value: purpose, location caveat, parameter guidance, and category hint. No fluff, front-loaded with the core action, and well-structured for quick scanning.

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?

The description covers the most important behavioral nuances (regional filter, fallback behavior, result contents, category helper), and an output schema exists for return values. However, it does not mention page size or pagination behavior for `max_pages`, and does not explicitly note that results may need dealer filtering, but overall it is sufficient for an agent to invoke the tool correctly.

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?

The schema provides no descriptions for any parameters (0% coverage). The description adds meaning for `locations` (regional, names from list_blocket_locations) and `category` (use list_blocket_categories), but does not explain `query` (obvious) or `max_pages` (defaults to 2). Since it covers only half the parameters and leaves the numeric control unexplained, it is useful but incomplete.

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 states 'Search Blocket.se for second-hand listings' with a specific verb and resource, clearly differentiating from sibling tools like search_tradera. It also adds the key scoping detail that the location filter is regional, not a precise radius, which helps distinguish its behavior.

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?

Provides explicit guidance to call list_blocket_categories() and list_blocket_locations() for category/location filtering, and explains the fallback behavior when locations are omitted. It does not explicitly contrast with other search tools (e.g., search_tradera), but the context is clear that this is for Blocket specifically.

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