obsidian_list_remove

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It states the basic removal action but does not mention permanence, behavior when a list or item is not found, side effects, or permissions. For a mutating tool, 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 two concise sentences with no redundant words. The first sentence states the purpose directly, and the second adds practical usage guidance. Every sentence earns its place.

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?

For a simple tool with two plain string/array parameters and an output schema, the description covers the core purpose and usage, including a helpful precaution about list names. It lacks some behavioral details, but given the tool's simplicity and the existence of an output schema, it is reasonably complete.

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 0%, so the description must compensate. It does clarify that 'items' are removed one or more at a time and that 'list_name' refers to an exact named list. However, it does not provide details on string formatting, whether items must already exist, or any constraints, leaving some gaps.

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 ('Remove'), the resource ('Obsidian list'), and the scope ('configured default vault'). It distinguishes itself from sibling tools like obsidian_list_add and obsidian_list_update by focusing specifically on removal.

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?

It explicitly says to use when the user asks to remove items from a named list, and provides a conditional prerequisite to call obsidian_list_lists if the exact list name is uncertain. This gives clear usage context and points to a relevant alternative/verification step.

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