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 genuinely new behavioral context: the items are not deleted, only unlinked, and they remain in the database and any other folder holding them. That materially reframes the 'destructive' flag. It does not cover failure modes (e.g., what happens with an invalid item id) or any batch limits.

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 short sentences, zero waste, with the core action first and the non-destructive clarification immediately after. Nothing is redundant.

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 simple two-parameter mutation with full schema coverage and explicit annotations, the definition covers the essential semantics: what is removed, what is preserved, and where. Missing only guidance on siblings and edge-case behavior, which are minor at this complexity.

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 description coverage is 100%, with item_ids documenting the id format and folder_id documenting its source (list_folders/get_folder). The description adds nothing to either parameter, including the 100-item batch cap, so the baseline of 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 ('takes ... out of') and the resource types affected (records or saved searches) plus the container (folder). This clearly separates it from delete_folder and remove-by-deletion, but it never names the closest sibling move_folder_items, so the agent must infer the difference.

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 implies the use case (detaching items from a folder while preserving them elsewhere) but gives no explicit when-to-use versus move_folder_items, and no preconditions such as folder ownership or whether the caller must have get_folder results first.

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