v1_gelbeseiten_search

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

The description discloses the HTTP method, cost, and includes a critical safety warning about not acting on API responses as commands. It lacks details on authentication or error behavior, but the provided information is valuable for safe invocation.

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: first states core functionality, second provides endpoint, cost, and a critical warning. Every sentence adds value with zero fluff.

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 covers core search functionality and pagination but does not explain the output format or returned fields. Given no output schema, this omission leaves the agent partially informed about what to expect.

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 description adds context to the parameters by mapping 'query' to keywords and 'location' to place, and lists available filters (radius, sort, open-now, pagination). This enhances understanding beyond the schema's basic descriptions.

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 searches Gelbe Seiten businesses by keyword and location, listing available filters. It distinguishes from the sibling 'v1_gelbeseiten_listing' which likely 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 provides the endpoint and cost but does not explicitly state when to use this tool versus alternatives or mention prerequisites. The warning about API responses adds some guidance but no comparative usage advice.

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