monday_archive_board

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

No annotations provided, and the description only contains routing boilerplate. It does not disclose behavioral traits such as reversibility, permissions needed, or side effects of archiving a board.

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 concise but includes irrelevant routing details. It front-loads the operation name but lacks structured 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?

Given the tool's action (archiving a board), the description is too sparse. There is no output schema, no examples, and no explanation of the archiving process, leaving the agent underinformed.

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?

The single parameter 'arguments' is a JSON string with no specified structure. The description provides no hints about required keys, making it impossible for the agent to know what to supply.

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 name 'monday_archive_board' and the description mention 'archive_board', but do not clarify what archiving entails (e.g., hides, moves, or deletes the board). This leaves ambiguity for the agent.

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 use this tool versus alternatives like monday_delete_board or monday_duplicate_board. The agent cannot determine appropriate context.

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