bulk_upload_remove_data_list

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only states the action ('Bulk remove') without clarifying consequences, such as whether removal is permanent, what happens if entries are not found, whether the operation is idempotent, or how partial failures are handled. For a mutation tool with no annotation safety signals, this is insufficient transparency.

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 with no unnecessary words or fluff. It efficiently conveys the core purpose and action, earning a perfect score for conciseness and structure.

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 the tool is a mutation with no annotations, no output schema, and an optional 'data' parameter, the description lacks critical context. It does not explain what happens when 'data' is omitted (e.g., does it remove all entries?), nor does it mention expected return values, error handling, or prerequisites like requiring the data list to exist. The minimal description is not complete enough for an agent to invoke the tool correctly in all scenarios.

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?

The input schema already provides descriptions for both parameters (id: 'Data list ID', data: 'CSV data to remove'), giving 100% schema description coverage. The description does not add any additional meaning beyond what the schema provides; it merely restates the action on a 'data list.' Baseline of 3 is appropriate because the schema does the heavy lifting.

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 action ('Bulk remove entries') and the resource ('a data list'), using a specific verb and scope. It distinguishes itself from sibling tools like delete_data_list (which deletes the entire list), bulk_upload_add_data_list (which adds entries), and bulk_upload_replace_data_list (which replaces entries). The name reinforces this distinction with 'remove' in the tool name.

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?

Usage is implied by the tool name and description: use when you need to remove multiple entries from an existing data list without deleting the list itself. However, the description does not explicitly state when to use this tool versus alternatives like delete_data_list or bulk_upload_replace_data_list, nor does it mention exclusions or prerequisites. No explicit guidance is provided beyond the basic action.

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