Dashboards: promote to default

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description goes well beyond them: it explains exactly what is overwritten (the project default), what is preserved (the source dashboard), who is affected (new users and anyone without a home dashboard), the admin requirement, and that it needs user confirmation.

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-loaded with the action and constraint, and every sentence carries operational weight. The clause explaining what the default is slightly restates the opening sentence, a minor redundancy in an otherwise tight four-sentence definition.

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?

For a one-parameter destructive admin tool with no output schema, the description covers everything an agent needs: effect, scope, side effects, permissions, confirmation guidance, and the sibling alternative. Nothing material 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 coverage is 100% and the schema already tells the agent the id is a dashboard ID discoverable via dashboards_list. The description only implicitly clarifies that the id refers to the source dashboard being copied rather than the target, 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 (copy a dashboard onto the project default) plus scope (new users' starting dashboard) and an access gate (administrators only). It is unmistakably distinct from siblings like dashboards_set_home, dashboards_update, and dashboards_create.

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?

Explicitly names the alternative for a closely related goal: 'To change only your own landing dashboard, use dashboards_set_home.' It also states the admin-only prerequisite and warns to confirm with the user before running, so both when-to-use and when-to-avoid are covered.

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