remove

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

With no annotations available, the description discloses an important side effect: from_disk=True deletes files from disk. It also notes this applies only to downloads, which is a useful scope restriction. Missing details include whether removal is permanent, what happens to associated metadata, or required permissions, but the key destructive behavior is surfaced.

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 extremely concise: two short sentences, front-loaded with the primary purpose and one crucial qualifier. Every word contributes value with no redundancy or fluff.

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 four optional parameters, no annotations, and no output schema, the description is markedly incomplete. It fails to explain how to specify what to remove (link_ids vs package_ids), what stage options exist, or what the tool returns. An agent would struggle to construct a correct invocation beyond guessing from param names.

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%, so the description must explain parameters. Only from_disk is partially explained (its effect on files), while stage, link_ids, and package_ids are left completely undefined. The description does not clarify the distinction between link_ids and package_ids or valid values for stage.

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 primary action ('Remove items from a list') and the from_disk qualifier, which distinguishes it from sibling tools like add_links and move_to_downloads. However, 'list' is generic and does not specify whether it targets linkgrabber or downloads, leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives such as reset or move_to_downloads. It only mentions a constraint (from_disk applies 'downloads only') but does not explain selection criteria or exclusions. This is insufficient for an agent to decide between siblings.

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