Start DataLens workbook import

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

Annotations only say non-readOnly, non-idempotent, openWorld. The description adds substantive behavior beyond that: the workbook materializes immediately and is populated asynchronously, connections arrive stripped of secrets, and a CONN.CHECK_CREDENTIALS notification signals this. This is exactly the kind of context the annotations cannot convey.

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 short sentences, front-loaded with the action and its return value, then the async/credential caveats. Slightly dense with backticked identifiers and the truncated '…CONN.CHECK_CREDENTIALS' token, but no sentence 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?

There is no output schema, and the description compensates by stating what is returned (import and workbook ids) plus the asynchronous lifecycle and the credential gap an agent must close. Nothing needed to call and follow through on this tool is missing.

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 the schema already documents all four parameters including the nested `data` object. The description's note that `data` is the output of workbookexports_result_get is useful but largely duplicates the schema wording, 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 and resource ('Start making a workbook from an export') and explicitly ties itself to the export flow, distinguishing it from datalens_workbookexports_start and datalens_workbookimports_status_get. An agent can identify the tool's role without opening the schema.

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?

The description spells out the full operational sequence: start the import, poll workbookimports_status_get until status is success, then re-supply credentials via connections_update. It names the alternatives/follow-ups and the conditions that select them rather than leaving the workflow to inference.

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