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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions a source preference but doesn't reveal ordering, filtering behavior, language handling, pagination, or any limitations. This is a significant gap for a search tool with no output schema or annotation hints.

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?

The description is a single, focused sentence that immediately communicates the tool's purpose and a key differentiator. Every word adds value; there is no filler or redundancy.

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 tool has three optional parameters, no output schema, and no annotations, so the description must cover more ground. It explains what the tool does but not what it returns, how it handles empty input, or how it interacts with sibling tools. This leaves substantial ambiguity for an agent deciding when and how to invoke it.

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 all parameters are already described in the schema. The description adds only the trusted-source context, which indirectly guides parameter usage (e.g., searching for a product name). It does not add deeper semantics like interaction between category and product or default behavior when no parameters are provided.

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's function: finding product test and review articles. It also mentions a differentiator by highlighting trusted sources (Stiftung Warentest, CHIP, IMTEST). However, it doesn't explicitly distinguish itself from closely named siblings like 'review_search' or 'warentest_search'.

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 guidance on when to use this tool versus its siblings (e.g., review_search or warentest_search). The description implies it is for product test/review articles with trusted sources, but it doesn't provide explicit use cases, exclusions, or alternatives.

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