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

With no annotations, the description carries full burden and delivers: caller becomes owner, board lands in the caller's personal namespace with a fresh unique code, source read-access requirement, and that authorization is 'enforced imperatively in execute'. These are exactly the side-effect and permission traits an agent needs before calling a mutation tool.

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 core action and the copy/exclude semantics before secondary details (ownership, namespace, authorization). Dense but each sentence carries information; only slight tightening would be possible.

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?

No output schema exists, and the description does not describe the return value (e.g., the new board's id/code), which is a minor gap. Otherwise it is complete for a clone mutation: source, resulting content, ownership, and authorization are all covered.

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 already documents code (auto-generated if omitted) and title ('<source title> (copy)'). The description adds only the framing of a 'fresh unique code', so it adds little beyond structured fields — baseline 3.

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 with explicit scope: clone a board copying 'the workflow not the data: statuses + board files + board title', and it enumerates the exclusions (tasks, comments, members). This clearly distinguishes it from create_board and other board-mutating siblings.

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 copy/exclude breakdown implicitly tells an agent when this tool applies (duplicating a workflow template) rather than create_board or update_board. It states the authorization conditions (board member OR any viewer of a public board), but never names an alternative tool explicitly.

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