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

No annotations are present, so the description must carry behavioral information. It explains the residential flag for hard antibot but does not describe return format, error handling, or how it differs from fetch_web in practice. Some expected behavior is implicit but not fully disclosed.

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 concise, using one sentence to convey the purpose and the key flag. No unnecessary wording 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?

Given the sibling tools, the context is fairly clear: it is the Russian-specific fetch tool. However, it does not mention edge cases like non-Russian sites or fallback behavior, but the specialization is sufficient for most use cases.

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 schema provides no parameter descriptions (0% coverage). The description only explains residential=true; url and agent_id are left undefined. Since the schema does not clarify these, the description fails to compensate for the missing parameter semantics.

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 fetches content from Russian sites through a Russian IP, with a specific use case for hard antibot via residential=true. It distinguishes itself from sibling tools like fetch_web (general) and get_ru_proxy (proxy provisioning).

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 implies usage for Russian sites and mentions when residential=true is needed, but it does not explicitly state when to choose this over fetch_web or get_ru_proxy. Still, the specialization is evident from the country parameter and Russian IP mention.

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