List DataLens cloud environments

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds real value by disclosing automatic pagination (no cursor management needed), experimental API status (a stability caveat), and the empty-list behavior for instances with no environments. It stops short of saying whether filters silently narrow results or how the response is shaped.

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 short sentences with the resource front-loaded and no padding. The phrasing of the final sentence is slightly awkward ('An instance with none answers an empty list'), but nothing is wasted.

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 output schema and full schema coverage on all parameters, the description covers the essential behavioral facts: auto-pagination, experimental status, and the empty-result case. It leaves the exact pagination mechanics and filter behavior to the schema, which is acceptable for this simple read tool.

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 three well-documented optional parameters (limit, filter, include_permissions), so the schema carries the semantics and a baseline 3 applies. The description contributes nothing about limit, filter syntax, or what include_permissions returns, so it adds no meaning 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 names the resource precisely (cloud environments of the DataLens instance) and the auto-pagination note confirms it returns a collection rather than a single item, distinguishing it implicitly from datalens_cloudenvironments_get/create/update/delete. It never states an explicit verb like 'list all', so the differentiation from siblings is inferred rather than declared.

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 when-to-use guidance and no alternatives named; an agent is not told to use this tool to enumerate environments and reach for datalens_cloudenvironments_get when a single environment is wanted. The only usage-adjacent information is the empty-list edge case.

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