keyso_get_report_ads_rsya_domains_domain

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 of behavioral disclosure, but it only states the purpose and shows a request example. It omits auth requirements (the token parameter appears only in the schema), rate limits, pagination semantics, and response characteristics.

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?

Four short lines with the purpose front-loaded, followed by method, path, and a concrete example. The example is slightly verbose with URL-encoded values, but there is no wasted prose.

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 seven parameters, no output schema, and no annotations, the burden falls entirely on the description, which omits the response format, accepted filter values (it only references a docs section), and authentication details. This is inadequate for an agent to call the tool correctly and safely.

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%, so the baseline is 3. The example URL demonstrates `sort=found_at%7Casc`, `page=1`, and `per_page=25` in real usage, adding slight value beyond the terse schema descriptions, but the description itself adds no new 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?

Объявления в РСЯ сайта names a specific resource (ads in the Yandex Advertising Network) scoped to a domain, and the path template `/report/ads/rsya/domains/<domain>` confirms the intent. However, the description does not differentiate it from the sibling `keyso_get_report_ads_rsya`; the agent must infer the per-domain scope from the name and path alone.

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 on when to use this tool versus alternatives such as `keyso_get_report_ads_rsya` or other report siblings. There are no exclusions, prerequisites, or selection criteria stated anywhere in the description.

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