List DataLens Spark resource presets

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint), so the bar is lower, yet the description still adds real value: it discloses auto-pagination, the default item cap behavior, and that this is an experimental, unmeasured API. That experimental caveat is exactly the kind of context an agent cannot infer from the schema or annotations.

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?

Two short sentences with no padding, and the cap/pagination constraint is stated plainly. The opening clause is a noun phrase rather than a verb, which slightly weakens front-loading but costs little.

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 small read-only list tool with no output schema, the description covers resource meaning, pagination, the limit/cap interaction, and experimental status. It does not mention the required environment scoping, but the schema carries that cleanly.

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 only two parameters, so the schema already documents both limit and cloud_environment_id in detail. The description's remark about the item cap reinforces the limit parameter but adds no syntax or semantics beyond what the schema states, so the baseline 3 applies.

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 defines the resource precisely ('the sizes an instance of a Spark cluster can take'), which tells an agent what a resource preset is, and the title supplies the 'List' verb. It does not explicitly differentiate itself from the singular sibling datalens_sparkclusters_resource_presets_get or the trinoclusters variant, so it stops short of a 5.

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?

It hints at how to control result size ('capped at the configured item cap unless limit is given') and notes pagination is automatic, which is useful call-time guidance. However, there is no explicit when-to-use vs. the _get sibling or the trinoclusters presets tool, and no stated prerequisites (the required cloud_environment_id) despite the tool being scoped per environment.

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