Detach a REST catalog from a DataLens Trino cluster

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond them: it clarifies that the catalog resource survives the detach (disambiguating 'destructive'), and it honestly discloses that the operation is experimental, undocumented-in-practice, and never actually exercised — a reliability caveat an agent needs.

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 its key scope constraint, with the experimental caveat kept tight. No filler.

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 two-parameter mutation with no output schema, the description covers action, scope, and reliability caveat. It could say more about what happens to the cluster's state or required permissions, but it is close to complete.

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% for both parameters (cluster_id, catalog_id), so the schema already carries the semantics. The description adds nothing about parameter format, id syntax, or constraints, so 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?

States a specific verb ('Detach') and resource ('REST catalog from a Trino cluster') and immediately scopes it against the nearest confusion point with 'the catalog itself stays.' An agent can distinguish this from datalens_trinoclusters_catalog_create or the datalens_restcatalogs_* siblings without opening either schema.

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?

Usage is implied by the name and the 'catalog itself stays' clause, but the description names no alternative tool or condition (e.g., when to detach vs delete the catalog, or how to reattach with catalog_create). No explicit when/when-not guidance.

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