Archive or delete an item

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

Discloses that archiving is undoable in the monday.com UI while delete removes the item permanently and requires confirm=true. This adds important safety and reversibility context beyond the destructiveHint annotation.

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?

Two concise sentences, front-loaded with the default behavior, with no fluff or redundancy. Every phrase earns its place.

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 operation with no output schema, it fully communicates default behavior, undoability, permanent deletion, and the confirm requirement. The schema and annotations cover the remaining parameter details.

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 coverage is 100%, so baseline is 3. The description enhances mode semantics by explaining the real-world effect of archive vs delete and the confirmation requirement, adding meaningful context beyond the schema.

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 it archives an item by default and can permanently delete the item with mode=delete. Clearly distinguishes from sibling tools by being the removal/archival operation rather than update or move.

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 says archive is the default and delete should only be used when the user asks, with confirm=true. Does not name alternative tools, but the mode-level guidance is clear and sufficient for selection.

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