Help improve this service: tell us what you need. question is one of: need_data (which Russian data sources you need), why_no_pay (if you didn't pay: price/payment_friction/ just_exploring/not_now), missing_service (what's missing), country_need (which country IP). Short answer.
| Name | Required | Description | Default |
|---|---|---|---|
| answer | Yes | ||
| agent_id | Yes | ||
| question | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It states that the answer should be 'short,' but does not disclose behavioral traits such as whether the tool is read-only or destructive, side effects, or authentication requirements. This is a significant gap for a submission tool.
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 extremely concise: two sentences with no unnecessary words. It front-loads the purpose and then lists the specific options efficiently.
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 3-parameter tool with no output schema and no annotations, the description adequately explains the question parameter and answer style. However, it omits context like what happens after submission (e.g., confirmation, storage) and any prerequisites. It is minimally complete.
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?
With 0% schema description coverage, the description compensates partially. It explains the 'question' parameter with valid values and their meanings, and hints that 'answer' should be short. However, it does not explain 'agent_id', leaving one parameter completely 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 states the tool's purpose: 'Help improve this service: tell us what you need.' It explicitly lists the survey questions, making the action (submitting feedback) unambiguous. The sibling tools are unrelated (check_balance, fetch_web, etc.), so there is no confusion.
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 clear context by enumerating the valid question options (need_data, why_no_pay, etc.), which guides when to use each. It does not explicitly state when not to use the tool or compare to alternatives, but the sibling tools serve different purposes, making guidance sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but fetch_ru and fetch_web overlap in functionality (fetch_ru is a specialization). However, descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., check_balance, fetch_web, topup_balance). Minor deviation like run_code is still in line.
9 tools cover the core functionality well without being excessive or insufficient. Each tool has a clear role.
Covers key operations: fetching, proxy, domain management, balance, code execution, and feedback. Missing advanced features like proxy rotation or pagination but sufficient for primary use.