Delete DataLens HTML page

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no statement about permanence, cascading effects on dependent dashboards, or required authorization. It neither contradicts nor enriches the 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?

A single short, front-loaded sentence — structurally clean with no padding. It is arguably too terse for a destructive operation, but there is no waste to trim.

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 simple one-parameter delete with rich annotations and no output schema, the description is technically sufficient to invoke the tool. It is missing any warning about irreversibility or side effects, which is material for a destructive operation, but annotations carry the core safety signal.

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 the single entry_id parameter, so the schema carries the parameter meaning and baseline 3 applies. The description 'Entry id.' in the schema is itself minimal, but the description text adds nothing further.

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 states a specific verb and resource ('Delete an HTML page'), so the operation is unambiguous. However, it is essentially a restatement of the tool name/title minus the vendor prefix and adds no distinguishing detail versus siblings like datalens_htmlpages_update or datalens_htmlpages_preview_url_get. Minimum viable rather than genuinely helpful.

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 tool, no mention of prerequisites or permissions, no warning about irreversibility, and no reference to alternatives (e.g. update vs delete). The agent gets zero routing help.

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