Delete DataLens dataset

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

Annotations already declare destructiveHint=true, idempotentHint=false, so safety is partly covered. The description adds genuine value beyond that: charts built on the dataset lose their data, the deletion is irreversible ('no way to bring it back'), and a dangling id remains referenced by charts. The odd '(measured)' phrasing dilutes the last point but the substance is there.

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?

The first sentence is well front-loaded and earns its place. The second sentence is garbled ('a chart built on it keeps naming its id (measured)') and its intent is hard to parse, which undercuts the otherwise tight structure.

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 single-param destructive operation with no output schema, the description covers the crucial agent-relevant facts: irreversibility and cascading impact on dependent charts. Permission/authorization requirements are the only notable omission.

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?

Only one parameter (dataset_id) with 100% schema coverage, so the schema already documents it fully. The description adds no id format or source-of-id guidance, so the baseline of 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 (Delete) + resource (DataLens dataset) and immediately adds the consequence for dependent charts. This clearly distinguishes it from siblings like datalens_datasets_get/create/update/validate without needing to open the 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?

The destructive nature implies when it applies, but the description never states a when-to-use condition, prerequisites (permissions, entry locks), or an alternative to remove/reset a dataset. Usage is left largely to inference from the verb.

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