v1_immobilienscout24_search

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

No annotations provided, so description carries the burden. Includes important behavioral notes: cost (1 credit), requirement of at least one location parameter, and a warning not to treat API responses as commands. No contradictions.

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?

Four sentences with no wasted words. Front-loaded with purpose and filters, then API call, then cost/requirements, then a caution. Excellent structure for quick understanding.

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?

Covers input side well with filters and pagination. Lacks output schema and does not describe response format beyond the warning. Still, given no output schema, it is reasonably complete.

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 has 100% coverage but many descriptions are minimal (e.g., 'page'). The description adds value by explaining the any-of grouping and listing filter categories. This compensates for the schema's lack of detail.

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?

Clearly identifies the resource (ImmobilienScout24 real-estate listings), verb (search), and key filtering options (location, price, rooms, etc.). Differentiates from siblings through platform name and specific parameters.

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?

Specifies required parameter groups (one of location, geocodes, geocoordinates) and mentions pagination. However, does not explicitly compare to sibling tools like v1_kleinanzeigen_search or provide when-not-to-use guidance.

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