Популярные поисковые запросы

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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses important behavioral details: requires confirmed permissions ('Требует подтверждённых прав'), specific error 404 HOST_NOT_INDEXED, top size cap (3000) and pagination limits. These are not visible in structured data and add significant transparency.

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?

Three dense sentences, each covering meaningful info: return format, limits/pagination, defaults, and error/auth. No filler or redundancy; front-loaded with the main purpose.

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?

For a tool with 8 parameters and no output schema, the description covers the response structure, pagination, default period, required permissions, and a specific error. This is highly complete, especially since the schema already documents all parameters.

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 baseline is 3. The description adds value by clarifying pagination semantics ('листайте offset/limit') and explaining the 3000-query top cap, which helps understand the offset/limit parameters. This goes slightly beyond what the schema provides.

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 clearly states it returns the top search queries for a site over a period, with a specific verb ('Возвращает') and resource ('ТОП поисковых запросов сайта'). It also details the response structure (queries array with indicators), which fully clarifies the tool's function.

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 context on default period and pagination ('По умолчанию период — последняя неделя', 'выдача — до 500 за раз'), but does not explicitly mention when to use this tool instead of alternatives like get_search_queries_history. Implied usage is clear, but no exclusions or alternative references are provided.

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