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

No annotations exist, so the description carries the full burden, yet it discloses nothing about pagination behavior (limit max 1000 / offset), permission needs, or result size. The only added context is that groups and target URLs are included in the payload, which the output schema likely already covers.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity leaves gaps that more content would have to fill rather than being a model of well-structured completeness.

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?

An output schema exists, so return values need not be spelled out, but for a paginated list tool in a crowded keyword-tool family the description does not say how results are paginated or ordered, nor how it differs from sibling keyword retrievers. Adequate but with clear gaps.

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%, with limit, offset, and project_id each documented in-schema, so the baseline is 3. The description adds no syntax, default, or ordering/pagination semantics 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?

States a specific verb and resource ('Получить ключевые слова проекта') and names the returned content (groups, target URLs). It does not explicitly distinguish itself from near-siblings like get_keywords_by_url, get_keywords_summaries, or get_project_keyword_groups, so it stops short of a 5.

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 call this rather than the many adjacent keyword tools (get_keywords_by_url, get_keywords_pages_summary, get_project_keyword_groups). Usage is only implied by the name, leaving the agent to infer selection among ~60 siblings.

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