monday_duplicate_board

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

Annotations already carry readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds useful context beyond these: the governing-authority routing restriction, the 'Spring verifies it' effect-checking mechanism, and the approval_ref line disclosing that writes may be resumed after an approval step. However, it never explains the actual operational behavior of duplication (what data is created/affected), leaving the destructive nature unexplained.

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?

The description is compact and the Args section is cleanly organized with no filler. However, the opening sentence duplicates information already present in the tool name and platform prefix, occupying space that could have explained the operation's behavior. Reasonably sized but not optimally front-loaded.

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 destructive write operation with 7 parameters and 0% schema coverage, the description is incomplete: an agent cannot construct the `arguments` JSON payload, does not know the approval flow required to execute the write, and is not told what board/workspace scope the operation targets. The output schema and annotations mitigate return-value and safety ambiguity, but the core invocation payload remains a black box.

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%, but the description's Args block does list all 7 parameters with terse one-liners, compensating at a baseline level. The critical gap is the `arguments` field: it is described only as 'JSON string of arguments for the connector operation' without any indication of what keys the payload requires (e.g., board_id, new board name), which is the actual operational contract. Several other descriptions ('Exact project correlation reference', 'Stable business-action identity') read as templated envelope boilerplate rather than domain-meaningful semantics.

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?

The description opens with 'Monday connector operation `duplicate_board`', which essentially restates the tool name rather than explaining what duplicating a board does (copies a board? its items? to which workspace?). It adds only the meta-context that this is a platform wrapper tool, not a functional description of the action or its outcome. This is close to a tautology.

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?

No guidance on when to invoke this tool versus the many other monday_* siblings (create_board, archive_board, update_item). The sentence 'Routes only through the exact project/account governed connector authority' is a routing constraint, not usage direction. There are no exclusions, prerequisites, or alternative-recommendations.

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