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

With no annotations, the description carries the full behavioral burden. It usefully discloses two traits beyond the schema: a 100-image-per-page ceiling and a 1-credit cost per call, which help an agent budget calls. It omits auth requirements, rate limits, and failure behavior, so it is adequate but not rich.

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 front-loaded sentences: purpose first, then the parenthetical return-field list and the cost/cap facts. No filler. Minor deduction for the slightly awkward '1 Credits' phrasing and for cramming result fields into a parenthetical rather than stating what a call returns in prose.

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?

There is no output schema, so the description correctly compensates by naming the returned fields, and it notes the per-page limit and cost. However, for a 10-parameter tool with only 60% schema coverage and no annotations, it says nothing about pagination beyond the 'page' param, rate limits, or how the filters combine — leaving gaps an agent would need to guess at.

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 60%, in the mid band. The description adds no meaning for any of the 10 parameters — it only lists return fields — but the seven enum parameters (size, type, color, layout, etc.) are largely self-documenting in the schema. Baseline 3 is appropriate given the schema does most of the work.

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 resource and source: 'DuckDuckGo Images for a query', and enumerates the returned fields (title, page url, image, thumbnail, width, height), so an agent knows exactly what it retrieves. It is clear on its own, but it never distinguishes itself from siblings like get_videos or get_news, so an agent must infer the boundary.

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?

There is no when-to-use guidance, no mention of when to prefer get_news/get_videos/get_places, and no prerequisites such as required auth or quota considerations. The only operational note is the page cap and credit cost, which is not usage routing.

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