keyso_get_report_simple_context_ads

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

No annotations are provided, so the description carries the full disclosure burden. It discloses the HTTP method GET and path, implying a read-only report, but it does not describe response contents, pagination behavior, required permissions, or the practical effect of the `full` parameter beyond the schema's one-line note.

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 and front-loaded: the resource label, method, path, and a concrete example request are all useful. It contains no filler, though the brevity leaves behavioral and usage gaps for other dimensions.

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 9 parameters, no output schema, and no annotations, an agent needs more than a path and example. The description omits what the returned report represents, default pagination values, and how this report relates to sibling context/direct ad tools, so it is not complete enough for reliable invocation.

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 illustrates the `sort` syntax and demonstrates the required `domain` along with `base`, `page`, and `per_page`, but it adds no meaning beyond the schema's field descriptions.

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 identifies the resource as 'Контекстная реклама - объявления' (context advertising ads) and provides the exact GET path, so an agent can map it to the context-ads report. It distinguishes from sibling tools like context_keywords and context_ads_links by naming 'объявления', but it never states an explicit verb such as 'list' or 'retrieve'.

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 gives only an example request and no conditions for when to choose this tool over the many sibling report tools such as context_keywords, context_ads_links, or direct_ads. There is no 'use when' statement, no exclusions, and no guidance about when this report is preferred.

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