Remove a bookmark

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description's job is lighter. It still adds non-obvious blowback: passing a folder guid removes the entire subtree, plus the advice to look the entry up first. It stops short of saying the removal is irreversible or whether any confirmation/undo exists.

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?

Three short sentences: the action and parameter first, the guid source second, the folder caveat last. No filler, no repetition of the title, and the riskiest detail is placed where it will be read before the call.

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 tool with no output schema and full schema coverage, the description covers action, input provenance, and the subtree side effect. There is nothing further an agent needs to invoke it correctly.

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?

Only one parameter and schema coverage is 100%, so baseline would be 3; the description earns extra credit by clarifying that the guid may refer to a folder as well as a bookmark, which the schema's 'Bookmark guid from browser_list_bookmarks' does not convey.

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?

States a specific verb and resource — 'Remove a bookmark or folder by guid' — and explicitly notes the underlying API call. It is clearly distinguishable from browser_list_bookmarks and browser_add_bookmark, which are named as the guid sources rather than as alternatives for this action.

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?

Tells the agent exactly where to obtain the required guid (browser_list_bookmarks for existing entries, browser_add_bookmark for freshly created ones), which is the main usage hurdle. It does not, however, name any alternative removal path (e.g. browser_bookmark_manage) or state when not to use this tool.

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