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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is carried structurally; the description still adds value by recommending a confirm-before-delete step. It does not say whether deletion is permanent, recoverable, or blocked when the palette is referenced by existing reports — the one behavioral gap that matters for a destructive call.

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 clauses, zero padding, with the action and its identifier front-loaded before the safety hint.

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 two-parameter destructive tool whose annotations declare the danger and whose schema fully documents inputs, the description plus a verification pointer is nearly sufficient. It omits the consequence of deletion (irreversibility, effect on reports using the palette), which is the remaining bit an agent would want.

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 both parameters document their source of truth (client_list, report_palette_list), so the schema does the heavy lifting. The description names paletteId as the target but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 ('Delete') and resource ('a palette') plus the identifying argument (paletteId), which cleanly separates it from the sibling palette tools report_palette_get/list/create/update.

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 routes the agent to report_palette_get first to verify the target before deleting, which is a real usage recommendation rather than a restatement. It stops short of stating when not to delete (e.g. a palette still in use by reports) or listing alternate destructive paths.

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