Stop DataLens Spark cluster

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

Annotation set already covers the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds genuinely new context: the call is asynchronous and returns an operation object that must be read via lakehouseoperations_get, plus an 'Experimental API, not measured' caveat. It does not describe rate limits or permissions, so not a full 5.

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, front-loaded with the action and immediately followed by the result-handling hint and the caveat. No wasted words.

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, the description adequately covers the return contract by pointing to lakehouseoperations_get, and flags the experimental status. Close to complete for a one-parameter mutation; only explicit permission/state prerequisites are 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 description coverage is 100% with a single required cluster_id, so the schema already carries the parameter meaning. The description adds nothing about the parameter beyond what is in the schema, which is the expected baseline.

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?

States a specific verb and resource ('Stop a running Spark cluster') that is inherently distinguishable from the sibling verbs start/delete/get. It does not explicitly name those siblings, but the operation is unambiguous.

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?

Implies usage ('a running Spark cluster') and routes the agent to datalens_lakehouseoperations_get to read the result, which is helpful. However it never states when to prefer stop vs delete or restart, nor any prerequisites beyond the implicit running-state condition.

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