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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds critical context they cannot convey: the deletion is irreversible ('cannot be restored'), the underlying boards/Pins are unaffected, and the call is mechanically refused unless confirm=true. This is exactly the extra information an agent needs before 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?

It is a single dense paragraph but front-loads the most important constraint (ONLY when explicitly asked) before the destructive semantics and confirmation mechanics. Every sentence carries operational weight; only the account-selection sentence is slightly tangential, though still relevant to correct invocation.

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?

With an output schema present and all three required parameters fully documented, the description only needs to cover prerequisites, side effects, and ambiguity handling — and it does all three. Nothing an agent needs to call this destructively and safely 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 parameter descriptions are already strong, so baseline 3 applies. The description still adds value by stating where boardListId comes from (list_board_lists) and framing confirm as a conversation-dependent gate rather than a plain flag; the accountId ambiguity guidance is likewise 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 a specific verb and resource (deletes the saved grouping by boardListId) and immediately clarifies the scope boundary: boards and Pins on Pinterest stay, only Tailwind's grouping is removed. That distinguishes it from delete_board and delete_board_section in the sibling list without the agent needing to open a schema.

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?

Explicit gating: 'Use this ONLY when the user has explicitly asked to delete one of their board lists', plus a required confirmation step and refusal behavior. It also supplies a fallback procedure when accountId is ambiguous (ask the user, never choose). Both when-to-use and when-not are stated.

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