DNS-Shop Search

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations, including the rendering environment, return format (price_rub is None not 0), and specific error conditions (TransportDownError, ParserDriftError). This is useful operational detail without contradicting the annotations.

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 compact and well-structured, opening with a clear purpose then using labeled sections for return and error formats. Each line adds meaningful information, avoiding fluff. Slightly verbose due to formatting details but appropriate for the tool.

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 simple one-parameter search tool, the description is highly complete. It covers purpose, return structure, and failure modes, and is backed by strong annotations and schema coverage. The tool is fully specified for an agent to select and invoke it correctly.

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 already provides 100% coverage with a description and example for 'query'. The tool description does not add further parameter-level detail, so the baseline of 3 is appropriate; the schema carries the semantic burden.

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 'Search DNS-Shop' with a specific verb and resource, making it distinct from sibling tools that target other marketplaces. It also adds context about being rendered in the operator's Chrome, further clarifying the tool's role.

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?

No explicit guidance is provided on when to use this tool versus alternatives like ozon_search or wb_search. The description does not mention exclusions or selection criteria, leaving the agent to infer that it should be used for DNS-Shop searches based solely on the name.

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