remove_content

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

With no annotations, the description must disclose behavior. It mentions 'Preview', 'removal', and 'confirmation', implying a two-step process, but lacks details on what the preview shows, whether the operation is destructive, or if it can be undone. The confirmationToken parameter hints at a confirmation mechanism but is not explained.

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 a single concise sentence that covers core functionality. It is not verbose, but it could be more structured to distinguish the preview and removal phases.

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?

Given 14 parameters, no output schema, and no annotations, the description is too brief. It fails to explain the workflow, return values, or side effects, leaving the agent with insufficient information to use the tool correctly.

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 0%, and the description adds no extra meaning to any parameter. It only says 'with confirmation', leaving 14 parameters unelaborated. While some parameter names are self-explanatory, the description does not clarify their roles or how they interact.

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?

The description clearly states the tool's purpose: 'Preview and remove queue or library items with confirmation'. The verb 'remove' and resource 'queue or library items' are specific, distinguishing it from sibling tools like add_new, queue_list, etc.

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?

No guidance is given on when to use this tool versus alternatives such as queue_list or search. There is no mention of prerequisites, when not to use it, or which workflow it fits into.

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