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

With no annotations provided, the description carries the full behavioral disclosure burden. It meaningfully discloses that only SEO-INDEX-passed products are returned and that NOINDEX, REVIEW, and collecting products are filtered out. It does not mention result ordering, pagination, or auth/rate limits, but the core filtering behavior is transparent.

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 two sentences with no filler. The core scope and exclusions are front-loaded, and every phrase adds useful information.

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 sufficient for understanding the tool's selection scope, but it is incomplete for confident invocation because parameter semantics are absent and there is no output schema to clarify the return shape. Given no annotations and no output schema, the description should provide a bit more operational detail.

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 input schema has 0% description coverage and the tool description provides no information about the query, category, or limit parameters. Parameter names are somewhat self-explanatory, but the description does not compensate for the missing schema descriptions, leaving semantics like accepted category values and query behavior undocumented.

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 identifies the verb ('search'), the resource ('HOTKER production catalog'), and the specific inclusion criteria ('SEO INDEX passed, latest products'). It also names exclusions ('NOINDEX, REVIEW, collecting'), making its purpose precise and distinguishable from sibling tools like search_verified_mobile_deals.

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 states what will and will not be returned, giving a clear scope boundary. However, it does not explicitly mention when to prefer this over alternatives or provide any exclusionary guidance for sibling tools, so the usage context is implied rather than explicit.

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