Remove images from a moodboard

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

Adds material behavioral context beyond annotations: the board is edited in place, there is no history, the action cannot be undone, and confirmation is required. This meaningfully supports the destructiveHint and helps the agent understand the risk.

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 two sentences with no filler. The first sentence states the function; the second provides the critical irreversibility warning. It is front-loaded and efficient.

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 mutation tool, the description covers the operation, the by-URL mechanism, in-place editing, irreversibility, and the confirmation requirement. The schema covers all parameters and annotations cover safety flags, so nothing essential is missing.

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%, and the schema already explains urls, confirm, and moodboard clearly. The description adds little beyond what the schema provides, so the baseline of 3 is appropriate.

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 the exact action and target ('Remove images from a moodboard') and the mechanism ('by URL'). The verb 'remove' clearly distinguishes it from siblings like add_to_moodboard and get_moodboard.

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 description gives a rationale for use ('Curation is the point of a moodboard, so this is how a board stays sharp') but does not explicitly name alternatives, when to prefer another tool, or when not to use this one. Usage is implied rather than explicitly routed.

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