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

Annotations only declare readOnlyHint=false, destructiveHint=true, openWorldHint=false; the description goes beyond them by disclosing what is excluded (members, comments, attachments) and the quota side-effect on owned-board limits. It does not describe the output (new board id/name) or permission-failure behavior, and the destructiveHint is left unexplained for an operation that arguably only creates.

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?

Three short sentences: the core behaviour first, then the omission list, then the quota caveat. No filler, no repetition of the tool title, and the most decision-relevant information leads.

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 single-parameter mutation with no output schema and annotations covering the safety profile, the description covers copy scope, omissions and side-effects. The remaining gap is the result of the call (new board's identifier) and error conditions, which are not documented anywhere.

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 0%, so the single boardId parameter carries no documented format in the schema. The description partially compensates by constraining valid inputs to boards the user can see, but it never states whether boardId is an id, slug or name, nor what happens if the board is not visible. Partial coverage of a one-parameter tool.

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+resource ('Copies a board ... into a new board') and enumerates exactly which sub-entities travel with the copy (lists, cards, content, dates, checklists, labels, look). This distinguishes it cleanly from create_board (blank board), duplicate_list and duplicate_task (sub-board scope) among the many 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?

Gives the precondition that selects this tool ('a board the user can see' → 'a new board the user owns') and a consumption caveat ('counts toward the free plan's 5 owned boards'). It does not explicitly route the agent away from alternatives like create_board or export_data, so it stops short of full when/when-not guidance.

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