keyso_get_report_group_list

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

Method GET and the full path /report/group/list are disclosed, which signals a read-only collection operation, and the example URL demonstrates query usage. However, with no annotations and no output schema, the description does not cover auth requirements, response format, pagination defaults, or error behavior.

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: a short label, method/path, and one illustrative example. There is no filler, though the first line largely restates the tool name and the example is the only material addition.

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 annotations and no output schema, the description should explain what the response contains, default pagination, auth expectations, and how this endpoint relates to the many sibling report tools. The current description is too sparse for an agent navigating a large tool set.

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 parameters are already fully documented in the schema. The description adds a concrete example URL showing sort, page, and per_page usage, which is helpful but does not substantially expand parameter semantics beyond the schema.

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 states 'Список групповых отчетов' (list of group reports), giving a clear verb and resource, and it is reinforced by the HTTP method and path. It is distinguishable from the numerous report_* siblings by its list scope, though it does not explicitly name a sibling or exclusion.

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 such as keyso_post_report_group or the various keyso_get_report_group_* endpoints. The description only provides the endpoint and an example request, leaving usage conditions and exclusions entirely to inference.

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