Create DataLens HTML page

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

Annotations already disclose the write/side-effect profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower. The description does add genuinely useful return-shape context — the created page under 'entry' and HTML validation feedback under 'warnings' — but says nothing about required permissions, side effects, or what happens on invalid HTML beyond warnings.

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?

One short sentence, front-loaded with the action and followed by the return-shape hint; no filler. It is perhaps too terse given the tool's complexity, but every clause carries information.

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?

With no output schema, the description's mention of 'entry' and 'warnings' is valuable, and annotations cover the safety profile. Still missing key context: the 'content' parameter is required HTML, placement in a workbook/folder matters, and nothing explains the relationship to the get/update/delete siblings.

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 every parameter (key, name, content, annotation, workbook_id) is already documented in the schema. The description adds no parameter-level syntax, format, or defaulting 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 and resource ('Create an HTML page'), which is clear and unambiguous. However, it does not differentiate from the many sibling tools, notably datalens_htmlpages_get/update/delete, beyond the bare verb.

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 datalens_htmlpages_update or datalens_workbooks_create, nor any mention of prerequisites such as needing a workbook_id or permissions. Usage must be inferred entirely from the tool name.

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