keyso_get_report_simple_direct_ads

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

With no annotations present, the description carries the full transparency burden. It reports the HTTP method and path and gives a sample request, but it does not describe response shape, authentication requirements, pagination behavior, error semantics, or any side effects beyond the generic 'get report' basis of the tool name.

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 compact: a one-line summary plus method, path, and a representative example. It is front-loaded and contains no filler; every line earns its place.

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?

Despite having eight parameters, many sibling report tools, and no output schema, the description provides only an endpoint summary and example. An agent is not told what fields or metrics the response contains, what the `kid`-based query means exactly, or how this report differs from the adjacent `..._context_ads` and `..._direct_domain` endpoints.

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 adds a concrete usage pattern (`base=msk&kid=...&sort=keys_count|desc&page=1&per_page=25`) but the description does not explain parameters beyond what the schema already documents.

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 resource ('Yandex.Direct ads') and the operation ('by query'/'по запросу'), with the HTTP path `/report/simple/direct/ads` reinforcing scope. It is clear enough to distinguish from the sibling `keyso_get_report_simple_context_ads`, though it does not explicitly contrast itself with alternatives.

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 given about when to choose this endpoint over sibling report endpoints such as `keyso_get_report_simple_direct_domain` or `keyso_get_report_simple_context_ads`. The example URL implies a typical call, but there is no stated condition, prerequisite, or exclusion.

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