Looker.Dashboard.Create

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

With no annotations, the description carries the full burden, and it does disclose that this is a guarded mutation requiring confirmation — meaningful context absent from the schema. Gaps remain: no statement of permissions, irreversibility, or side effects, and "validate_only" is named without a corresponding parameter in the schema, which risks confusing the agent.

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 the action first and the guard second — no filler. The parenthetical is dense 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?

An output schema exists, so return values need not be described, but for a guarded creation tool with zero annotations and zero parameter documentation, the description should explain the confirm-token flow and the missing validate_only parameter. As written, an agent knows it must confirm but not how to obtain or use that token.

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 0% across 3 parameters, so the description must compensate and it only partly does: "under a model" loosely anchors the model param and "confirm token" explains the confirm param's role. The required title parameter gets no semantics at all, and the token acquisition mechanics are unstated.

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?

Specific verb+resource ("Create a dashboard") with a scope qualifier ("under a model"), which is more than the title alone provides. It does not explicitly position itself against the Looker read siblings (looker.dashboards.list, looker.look.run, looker.query.run), so differentiation is left to the name.

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 parenthetical implies a two-step workflow (validate_only preview, then a confirm token), which is a real usage hint. However, it never states the ordering explicitly, never says when to choose this over the Looker read tools, and never explains where the confirm token comes from.

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