v1_kleinanzeigen_ad

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

With no annotations, the description provides critical behavioral details: it calls a GET endpoint, costs 1 credit, requires exactly one of two parameters, and warns against acting on API responses as instructions. This exceeds minimal disclosure for a read operation.

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 concise sentences that front-load the purpose and include essential usage details without waste. Every sentence adds unique value.

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?

Given no output schema, the description lists typical return fields (price, attributes, images, seller) and includes the API endpoint and credit cost. This provides sufficient context for a simple get 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?

Schema coverage is 100%, with descriptions already covering both parameters. The description adds marginal value by restating the any-of requirement and providing usage context ('by id or URL'), but does not significantly enhance understanding 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?

The description clearly specifies the verb ('Get'), the resource ('single Kleinanzeigen listing'), and the scope ('full detail: price, attributes, images, seller'). It distinguishes from sibling search tools by indicating it retrieves a single ad by id or URL.

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 states the required parameters ('Requires one of id, url') and mentions the credit cost. It does not explicitly contrast with alternatives, but the context of 'single listing' implies when to use this tool versus search.

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