List DataLens Trino clusters

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

Annotations already cover readOnly/idempotent/openWorld, so the bar is lower. The description adds real operational context beyond that: results are auto-paginated, the endpoint is experimental, and an instance with no clusters returns an empty list rather than an error — a genuinely useful non-obvious 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?

Three short fragments, zero filler, with the resource identification and the pagination behavior front-loaded. Nothing could be removed without losing information.

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 four-parameter read-only list tool with a fully documented schema and no output schema, the description covers the essentials: scope, auto-pagination, and empty-result behavior. Minor gap in not pointing to the sibling get tool or restating the filterable dimensions.

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 schema fully documents limit, filter, catalog_id, and collection_id; baseline of 3 applies. The description adds no meaning beyond the schema — e.g. it never mentions that filtering by catalog or collection is possible.

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 a specific resource (DataLens Trino clusters) with the listing semantics implied by the title and the 'auto-paginated' modifier. It is distinguishable from sibling datalens_trinoclusters_get, though the 'list' verb itself only appears in the name/title rather than the description body.

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 on when to call this versus datalens_trinoclusters_get or datalens_restcatalogs_list, and no prerequisites stated. The only contextual note is the experimental API flag and the empty-list case, neither of which tells the agent when this tool is the right choice.

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