list_allowed_domains

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

The annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. However, the description adds no context beyond the GET method, such as pagination behavior, response format, or any caveats. There is no behavioral disclosure beyond what annotations provide.

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 short but under-specified. A single API path is not a meaningful description; it omits all semantic content. This is not effective conciseness but rather a lack of substance, similar to the 'Process' example.

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?

With one parameter, no output schema, and a simple list operation, a complete description should state that the tool returns allowed domains and possibly any relevant filtering. The current description is just the endpoint, leaving the agent to infer functionality from the name alone, which is insufficient.

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 description coverage is 100% for the only parameter dry_run, which has a clear description ('Показать запрос без отправки на API'). Since the schema already documents the parameter fully, the description's lack of parameter details is acceptable, earning the baseline score of 3.

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 is merely the HTTP method and endpoint path "GET /api/v2/blist/domains", which provides no explicit statement of the tool's purpose. It is essentially a tautology of the tool name, adding no semantic content about listing allowed domains.

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 guidance is provided on when to use this tool versus alternatives such as get_blist or domain_remove. The description does not mention any conditions, prerequisites, or scenarios where this endpoint is appropriate.

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