v1_gelbeseiten_listing

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

No annotations exist, so the description carries full burden. It discloses the HTTP method, cost, and a safety warning about API responses being data, not instructions. However, it doesn't cover authentication or error handling.

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?

Three sentences, each essential: purpose, technical details (API endpoint, cost, requirement), and safety warning. No fluff, front-loaded with the core action.

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 is insufficient for the tool's complexity (8 params, no output schema). It ignores parameters like page, sort, query, radius, location, open_now, which may suggest broader functionality inconsistent with 'get one listing by id/url'. Return values are partially described but not fully.

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%, baseline 3. The description adds value by explaining the 'any-of' requirement for id/url and what the output includes (address, phone, etc.). It doesn't clarify other parameters (page, sort, query, etc.) but focuses on the key ones.

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 the tool gets one Gelbe Seiten business listing with full details (address, phone, website, rating, opening hours) by numeric id or URL. It distinguishes from sibling search tools by specifying it retrieves a single listing.

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 when to use (have id or URL) but does not explicitly mention alternatives like v1_gelbeseiten_search. The context of siblings suggests it's for retrieving details after search, but no direct guidance is provided.

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