kwfinder_update_list

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states that it updates a list name, but provides no information about side effects, required permissions, idempotency, error handling, or whether the operation is partial or replaces the entire list.

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, short sentence with no wasted words. It is front-loaded and easy to parse.

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 involves 4 parameters (including a nested body object), has mutation semantics, and no output schema. The one-sentence description is insufficient to understand the full context, such as what the response returns, how to structure the body, or what errors might occur.

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 all parameters (list_id, name, body, query), achieving 100% coverage. The description adds no additional parameter semantics beyond repeating the 'name' parameter's purpose. 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 ('Update') and the resource ('KWFinder list') with the specific field ('name'), which distinguishes it from sibling tools like create/delete list. It is specific and unambiguous, though it lacks additional nuance about the scope of the update.

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 kwfinder_create_list or kwfinder_add_list_keywords. It simply states the action without explaining prerequisites, when it should be chosen, or when a different tool would be appropriate.

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