v1_immobilienscout24_expose

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

With no annotations provided, the description adds useful behavioral information: it calls a GET endpoint, costs 1 credit, and warns that API responses are data not instructions. This goes beyond what the input schema provides, guiding the agent on safe usage.

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 concise: 3 sentences covering purpose, endpoint, cost, parameter requirement, and a safety note. Front-loaded with key information, no wasted words.

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 simple get-tool with no output schema, the description lists the types of data returned (price, criteria, images, etc.) and includes cost and safety instructions. It lacks exact field names but provides sufficient context for an agent to decide to use the tool.

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 input schema has 100% coverage with descriptions for both params. The description reinforces the mutual exclusivity requirement ('Requires one of id, url') and clarifies usage by id or URL, adding value beyond the schema's any-of group notation.

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 clearly states it gets a single ImmobilienScout24 listing with full details (price, criteria, images, etc.) by id or URL. It specifies the verb 'Get' and the resource 'listing', distinguishing it from the sibling tool v1_immobilienscout24_search which is for search.

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 indicates usage context: retrieving a single listing by id or URL. It mentions the cost and requirement to supply one of id or url. While it doesn't explicitly state when not to use it or alternative tools, the purpose is clear and the sibling search tool implies when to use this one.

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