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

Annotations declare readOnlyHint=false and destructiveHint=false, so safety profile is already covered. The description adds real value beyond that: it discloses the source-side effect ('Increments the source's fork counter') and the permission rule (public/unlisted any, private only if owned).

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 verb and lineage semantics, then use case, side effect, and permissions. Slightly dense with the em-dash aside and repeated 'fork' phrasing, but every sentence 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?

Output schema exists, so return values need not be described. The description covers purpose, context, side effects, and permission constraints; only an explicit alternative/edge case would be needed to be fully complete.

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%, and the schema documents all three params including defaults for name and visibility. The description adds no param syntax or format detail beyond that, so it meets the baseline of 3 rather than adding meaning.

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?

'Fork an existing dashboard into a new artifact you own, preserving lineage' gives a specific verb, resource, and outcome. It is clearly distinguishable from siblings like save_dashboard, update_dashboard, and search_dashboards.

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 states the intended context ('adapt a popular dashboard rather than build from scratch') and gives a concrete example, plus names update_dashboard as the follow-up for editing the fork. No explicit 'when not to use' or named alternative to forking, so short of a 5.

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