Create DataLens dashboard

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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true). The description goes beyond them by documenting the return ('with its id') and a concrete failure mode — the 400 error when entry.meta is omitted — which is genuinely useful behavioral context for a create call.

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?

Front-loads the purpose in one sentence, then adds the field requirements and error detail without padding. Every sentence carries information, though the backtick-heavy inline markup is slightly noisy.

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, mentioning that the created dashboard with its id is returned is necessary and present, and the nested-type gap is partly compensated by the data/meta field notes. Permissions and post-creation behavior are not covered, keeping it from a 5.

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%, but the sole parameter's real shape is an external type (DashboardCreate) not listed inline, so the description's detail that data needs counter, salt, settings and tabs, that a tab may be empty, and that entry.meta must be an object adds real meaning beyond 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 ('Create a dashboard') plus a return detail ('and return it with its id'), so it is clearly distinguished from the get/update/delete dashboard siblings by the verb alone. It stops short of naming an alternative tool, 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?

No explicit when-to-use/when-not guidance and no mention of prerequisites like required permissions or the relationship to datalens_workbooks_create. A careful agent can infer it creates a new dashboard, but the description offers no routing context.

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