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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavior: the result is a new, private dashboard owned by the caller, which implies the source is not modified and that sharing settings are not carried over. It does not state what happens to blocks/layout or what identifier comes back.

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 zero filler; every word (copy, dashboard, new, private, owned by you) 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?

For a mutation tool with no output schema, the definition should say what comes back (e.g., the new dashboard's ID) and whether the caller needs edit access on the source. It conveys the essential semantics but leaves these operational gaps for an agent that must chain the result into a follow-up call.

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 dashboardId (the source UUID) and title (the new name) are already documented. The description adds no format, constraint, or naming guidance beyond that baseline.

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?

"Copy a dashboard into a new private one you own" pairs a specific verb (copy) with the resource (dashboard) and states the outcome object. It is clearly distinguishable from report_create_dashboard and report_rename_dashboard, though it never names those siblings explicitly.

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 when-to-use or when-not-to-use guidance, and no mention of the near-alternative report_create_dashboard (build from scratch) or report_get_dashboard (inspect before copying). The agent must infer from the phrasing alone that this is the duplicate path.

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