Delete DataLens editor chart

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description goes beyond that by disclosing a cascade consequence — dashboards showing the chart lose it — which is exactly the kind of impact context annotations cannot express. It still omits whether deletion is permanent/undoable or requires elevation.

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?

A single clause, front-loaded with the action and immediately followed by the consequence. Nothing extraneous; every token earns its place.

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 one-parameter, no-output-schema delete tool with strong annotations, the description supplies the key missing piece — downstream impact on dashboards. It is nearly complete, only lacking reversion/permission notes that would round it out.

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%, so chart_id is already documented, establishing the baseline of 3. The description adds no format, ID-source, or lookup detail beyond the schema.

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 ('Delete a chart'), so the action is unambiguous. It does not distinguish this editor-chart delete from the sibling deleters datalens_charts_wizard_delete and datalens_charts_ql_delete, so an agent relying on the description alone cannot tell which chart type it targets beyond the name/title.

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 guidance on when to use this versus the wizard/ql delete siblings, nor any note about prerequisites such as ownership or permissions. Only the vague implication that deletion removes something is offered.

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