Create Dashboard

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 profile is covered elsewhere. The description adds nothing beyond that: no mention of required auth scope, whether name collisions are rejected or duplicated (relevant given idempotentHint=false), or whether the dashboard is immediately visible.

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 short sentence with no padding, but it is under-specified rather than economical — the one clause present ("from provided data") carries no information, so brevity here is a cost, not a virtue.

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?

The tool has a nested required payload and no useful description of it; the existence of an output schema excuses not explaining return values, and annotations cover side-effect hints, but the create contract itself (payload shape, uniqueness, ownership semantics) is absent. For a create operation in a large sibling set this is inadequate.

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?

The only parameter is a deeply nested `data` envelope with required `type`/`attributes` and required `name`/`owner`, yet the description contributes nothing about that structure. Even though several leaf fields carry schema descriptions, the top-level shape an agent must construct is undocumented in the description, so "from provided data" leaves real work unexplained.

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?

The verb+resource ("Creates a new dashboard") is unambiguous and clearly distinct from update_dashboard / list_dashboards / get_dashboard. However, "from provided data" is filler that says nothing about what a dashboard payload contains or what gets created, so the statement stops at minimum viability.

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 call this versus update_dashboard or how it relates to creating panels via update_dashboard_panel, and no prerequisites (permissions, ownership rules, whether the dashboard must be attached to a team) are mentioned. The agent must infer all routing decisions.

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