kwfinder_delete_list_keywords

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

With no annotations, the description carries the full burden. It indicates a mutating/destructive operation ('Remove') but does not disclose whether the deletion is permanent, whether multiple keywords can be removed at once, what happens to the list, or any required permissions. This is a significant gap for a delete operation.

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, direct sentence that immediately states the action and target. No wasted words; it is appropriately front-loaded and concise.

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?

The tool has a moderate complexity with optional generic parameters and no output schema, but the description provides almost no context about expected behavior, return values, or side effects. Given that keywords is not required in the schema, the description should clarify whether omitting it removes all keywords or is an error, but it does not.

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 75%, and the description adds minimal meaning beyond the schema. It clarifies that 'keywords' are the items to be removed, but the generic 'body' and 'query' pass-through parameters remain unexplained. The description does not fully compensate for the undocumented 'keywords' array.

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 uses a specific verb ('Remove') and resource ('keywords from a KWFinder list'), making the operation clear. It distinguishes itself from siblings like kwfinder_delete_list (delete whole list) and kwfinder_add_list_keywords (add keywords).

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: removing keywords from an existing KWFinder list. However, it does not explicitly mention when not to use it (e.g., use kwfinder_delete_list for deleting the entire list) or name alternatives, leaving the guidance to inference.

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