run_kleinanzeigen_listings

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

No annotations are provided, so the description carries the full burden. It does disclose one real behavioral trait beyond the schema — the flat 5-point cost per successful run — and enumerates the fields returned, but says nothing about auth requirements, rate limits, or failure/not-found behavior for an unannotated read tool.

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?

Two tight sentences with the core action and the returned fields front-loaded, then the cost note. No filler or redundancy.

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 one-parameter, no-annotation, no-output-schema tool the description is nearly sufficient: it names the input forms and summarizes the return payload, standing in for the missing output schema. Only error/edge-case behavior is unaddressed.

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% and the single 'ad' parameter already documents 'Ad ID or URL. e.g. 3517031976'. The description's 'by id or URL' merely repeats the schema, so baseline 3 applies.

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 and resource ('Get one Kleinanzeigen ad by id or URL') and enumerates the returned payload (price, description, location, attributes, images, seller). The singular 'one ad by id or URL' clearly separates it from the sibling run_kleinanzeigen_listings_search / _similar tools.

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?

Usage is only implied: the agent infers this is the tool for a known ad ID or URL. Nothing states when to prefer it over run_kleinanzeigen_listings_search (e.g., 'find the ID first with search') or what to do if the listing is gone.

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