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

With no annotations, the description carries the full burden and delivers meaningful traits: the upstream data source varies (Tripadvisor or Yelp, surfaced as `source`), the implicit-geolocation fallback, the country-disambiguation pitfall, and per-call billing (1 Credit). It omits anything about result limits, pagination, or failure modes.

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?

A single dense paragraph, front-loaded with what the tool returns before moving to invocation rules and cost. Every sentence carries information, though the run-on field enumeration is heavy and could be broken up for scanability.

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 tool with no output schema and no annotations, the description compensates well by enumerating the returned fields, naming the source-attribution field, and disclosing billing. Remaining gaps are minor: no mention of result caps or pagination, and no explicit statement that the call is read-only.

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%, so the baseline is 3; the description goes beyond it by explaining the q-vs-coordinates decision, that coordinates must be paired, and the default-address behavior when neither is supplied. It adds genuine interpretive value rather than restating the schema's field 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 opens with a precise resource definition: "DuckDuckGo's local results (its Places module and Maps tab)" and enumerates the returned fields, so an agent knows exactly what this tool yields. It implicitly separates itself from get_news/get_images/get_videos by scoping to local business listings, but never explicitly names a sibling or contrasts against the generic `get` tool.

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?

Gives concrete invocation guidance: name the place in the query ("coffee in berlin germany") or pass latitude/longitude, and warns that with neither DuckDuckGo geolocates from the request address, so a shared place name can resolve wrongly. It does not state when to prefer this over sibling search tools or any exclusion conditions, keeping it short of a 5.

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