keyso_get_report_simple_organic_keywords

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

With no annotations, the description must carry the behavioral burden. It discloses that this is a GET request and shows an example URL, which implies a read operation, but it does not describe the response shape, pagination behavior, or any operational constraints. This is insufficient for a 10-parameter endpoint.

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: title, method, path, and example. Every line earns its place and there is no filler or redundant 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?

There is no output schema and no description of return values, which leaves a significant gap. Given 10 parameters and many sibling report tools, the description does not provide enough context about filters, pagination defaults, or the meaning of includeSubLevels to be considered complete.

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 baseline is 3. The example adds a concrete usage pattern for domain, base, sort, page, and per_page, but it does not clarify opaque parameters like filter, includeSubLevels, base_url, or token beyond what the schema already states.

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 says 'Органическая выдача - ключевые слова' and provides the exact path, so it clearly points to an organic-keywords report. However, it lacks a verb and does not differentiate this endpoint from close siblings like keyso_get_report_simple_organic_keywords_bypage or keyso_get_report_simple_organic_lost_keywords.

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 on when to use this tool versus alternatives. The example request demonstrates one valid call, but no context, exclusions, prerequisites, or selection criteria are given.

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