List DataLens Spark clusters

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds genuinely useful context beyond that: auto-pagination behavior, the configured item cap (YCLI__HTTP__MAX_ITEMS), and the experimental/unmeasured status of the API.

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?

Short and front-loaded with the resource and pagination trait first. The phrase 'Experimental API, not measured: ycli follows its document' is somewhat cryptic and could be clearer, but the overall text is compact with little waste.

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 read-only list tool with annotations covering safety, 100% schema coverage, and no output schema, the description covers the essentials: what it lists, that results are paginated, and the item-cap behavior. Nothing critical to correct invocation is missing.

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 all three parameters (limit, filter, collection_id) are already documented in the schema. The description only reinforces the limit/cap behavior, adding little beyond what the schema provides; baseline 3 applies when the schema does the heavy lifting.

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 ('Spark clusters of DataLens') and the tool name/title carry the verb ('List'). It is clear what is returned, but it does not differentiate itself from siblings like datalens_sparkclusters_get or the other datalens_sparkclusters_* tools.

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 explicit when-to-use guidance, no exclusion conditions, and no reference to alternative tools. The agent must infer that this lists rather than fetches a single cluster (datalens_sparkclusters_get) or a resource preset list from the name alone.

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