edb_remove_bookmark

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds the return type (str: Confirmation) but does not disclose behavior for nonexistent bookmarks, side effects, or whether the action is reversible.

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 extremely concise, front-loaded with the purpose ('Remove a bookmark by name'), and every line earns its place without unnecessary detail.

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 one parameter and annotations, the description is adequate but has gaps: it does not specify what happens if the bookmark does not exist, nor does it elaborate on the confirmation string format. The sibling edb_list_bookmarks exists but is not cross-referenced.

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?

With schema description coverage at 0% (top-level params lacks description), the description compensates by explaining that the param is a 'Bookmark name' and the specific field 'name' is 'Bookmark name to remove'. This adds clarity beyond the schema.

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 'Remove a bookmark by name', specifying the action (remove) and the resource (bookmark) via a unique identifier (name). This distinguishes it from siblings like edb_add_bookmark and edb_list_bookmarks.

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 usage (when you want to remove a bookmark by name) but does not explicitly state when to use this tool over alternatives, nor does it mention prerequisites or error conditions.

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