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

Annotations are absent, so the description carries full responsibility for behavioral disclosure. It mentions a cost ($0.02 USDC), which is a useful trait, but does not explain side effects, return format, or read-only nature. This is minimal transparency for a tool that likely performs a network operation.

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 short sentence (in Russian) with no fluff. It conveys the core purpose succinctly, but the brevity sacrifices essential details, which is handled under completeness. As conciseness alone, it is efficient.

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?

Given the generic schema, lack of annotations, and no output schema, the description is severely insufficient. It fails to explain how to invoke the search, what parameters to provide, expected results, or any operational constraints. The complexity of the underlying tool is not reflected in the description.

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 0% – the input schema only defines wrapper objects with additionalProperties, providing no meaningful parameter definitions. The description adds no parameter information, so agents have no idea what to pass. This is a critical gap.

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 states the tool performs a web search specifically for Cyrillic content, which is a clear verb+resource. However, it does not explicitly contrast with sibling tools (inn_lookup, ru_page), so it lacks clear differentiation, though the purpose is understandable.

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 provides no guidance on when to use this tool versus alternatives. It merely states it is a Cyrillic web search, without indicating prerequisites, exclusions, or when a sibling would be more appropriate.

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