Remove (single)

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

The destructiveHint annotation already flags mutation, but the description adds that the operation cannot be undone and instructs the agent to confirm with the user. It also clarifies that only bookmarks or empty folders are valid targets, which is useful behavioral context beyond the annotation.

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?

Two tight sentences front-load the action and scope, then give the alternative and warning. Every sentence earns its place with no filler.

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 single-parameter destructive removal, the description covers purpose, scope, the sibling alternative, and the need for user confirmation. Return-value details are not essential for this operation and are not required by any output schema.

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 carry the parameter meaning. It implies the required id is the target bookmark or empty folder to remove, but it never explicitly maps id to 'the bookmark/folder identifier' or describes its format. For a single obvious id parameter this is mildly sufficient but not fully compensating.

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 the specific verb 'Remove' and names the exact resource scope: one bookmark or an empty folder. It also distinguishes itself from bookmarks_remove_tree, so an agent can tell them apart without inspecting schemas.

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 states a clear condition for using this tool ('one bookmark or an empty folder') and explicitly redirects non-empty folders to bookmarks_remove_tree. It also adds a usage prerequisite: confirm the target with the user before calling.

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