keyso_get_clustering_list

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

With no annotations, the description carries the behavioral burden. It does disclose 'Method: GET' and provides an example request, implying a read-only list operation. However, it does not mention response shape, pagination behavior, authentication expectations, or rate-limit considerations.

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 one-line purpose statement, method/path, and a concrete request example. There is no filler or redundant repetition of the schema.

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 simple GET-list endpoint with complete schema documentation, this is minimally adequate for constructing a request. However, there is no output schema or annotations, and the description does not describe the returned project objects or related clustering workflow steps, leaving some context 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?

All 6 parameters are fully described in the schema (100% coverage), so the baseline applies. The example URL demonstrates usage of sort, page, and per_page, adding minor concrete value, but it does not add meaning beyond what the schema descriptions already provide for token, base_url, or isMain.

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 opening phrase 'Список проектов кластеризатора' identifies the action (list) and resource (clustering projects), and the explicit 'Method: GET /clustering/list' makes the operation unmistakable. It does not directly contrast with sibling tools like keyso_get_projects or keyso_get_clustering_state_uid, but the endpoint path and resource scope are specific enough to distinguish.

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?

No guidance is given about when to use this tool versus related tools such as keyso_get_projects, keyso_get_clustering_state_uid, or keyso_post_clustering. The description states the endpoint but never explains when to prefer it or when to use a sibling instead.

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