keyso_get_report_simple_context_ads_facts

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does state Method: GET, which implies read-only behavior, and shows an example query, but it does not explain what data is returned, authentication needs, pagination behavior, or what 'unique facts' means.

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 includes the essential method, path, and example in a scannable format. The opening phrase is vague, but there is no padding or irrelevant content.

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 no output schema and no annotations, this tool needs a fuller description to be reliably invoked. The path and example are helpful, but the description does not explain the report semantics, response structure, filtering options, or how this fits with the broader report family.

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 coverage is 100%, so the schema already documents all parameters well. The description adds value by providing a concrete example request with realistic values for base, domain, sort, page, and per_page, including the URL-encoded sort format.

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's main phrase 'Контекстная реклама - объявления, уникальные факты' is a noun fragment that essentially restates the tool name without a verb or clear action. Method and path are given, but not what the endpoint actually returns or how it differs from the many similar context-ads sibling endpoints.

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?

There is no guidance about when to use this endpoint versus alternatives like keyso_get_report_simple_context_ads, keyso_get_report_simple_context_ads_links, or group-level fact endpoints. The example request shows how to call it, but not why an agent should choose it.

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