Update DataLens HTML page

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety bar is partly covered. The description adds genuinely new behavioral context beyond annotations: save leaves the published version untouched, publish is user-visible, and revId+save copies a revision into the current draft.

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?

Three compact sentences, front-loaded with the purpose before the mode semantics, and every clause carries information an agent needs. No filler or restatement of the title.

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 polymorphic body parameter this is nearly complete: both oneOf branches and all three mode/enum semantics are explained, and no output schema exists to require return-value documentation. It omits only peripheral concerns such as permissions or revision-retention behavior.

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 coverage is 100%, so the baseline is 3, but the description goes beyond the schema's terse 'HTML page update mode' by defining what save vs publish actually do and by clarifying the revId branch resolves to the second oneOf shape ('one of the two, not both' is also restated in 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 ('Save new HTML of a page, or make one of its revisions the current one') and covers both entry paths, so an agent can tell this apart from datalens_htmlpages_create/get/delete. It never names a sibling alternative explicitly, so it lands at 4 rather than 5.

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?

Gives real mode-selection guidance: 'save' makes a new revision and leaves the public one, while 'publish' shows it to everyone, plus the revId-with-save case. That is clear when-to-use-which guidance for the two modes, though it offers no exclusions or pointers to the create/delete siblings.

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