Create DataLens editor chart

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety/mutation profile is covered. The description adds one useful behavioral fact – that the created chart is returned with its id – but says nothing about permissions, validation failures, or side effects on the target workbook.

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 front-loaded sentence with no filler; it is efficient. It is arguably too terse for the complexity involved, but nothing in it is wasted.

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?

Annotations cover the safety profile and the schema is fully self-documenting, which lowers the burden. Still, for a tool with a very large polymorphic schema and no output schema, one sentence leaves important context (which chart kinds exist, that 'entry.type' selects the variant, and where the entry must live) unstated in the prose.

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% and the single nested 'entry' parameter is exhaustively documented, including the discriminator const values. The description adds nothing beyond the schema, so the baseline 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 ('Create') and resource ('a chart of the editor'), so the agent knows this is a write/create operation on an editor chart. It does not, however, distinguish itself from close siblings like datalens_charts_wizard_create or datalens_charts_ql_create, leaving the agent to infer which chart flavor applies.

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 when-to-use guidance, no prerequisites (e.g. that a workbook or key must be supplied), and no mention of alternatives among the many sibling create tools. The agent gets no routing help at all.

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