remove_bookmark

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

Discloses that paragraph content is retained, which is key behavioral info. No annotations are provided, so description carries full burden; however, it lacks details on error states (e.g., missing bookmark) or permissions.

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?

Single sentence with the verb first, efficiently conveying action and a critical side effect. No wasted words.

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?

Tool is simple with one parameter; description covers the primary behavior and uses output schema (not shown) to handle return values. Minor gap: no mention of error handling for missing names.

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?

Single parameter 'name' has no schema description (coverage 0%). Description identifies it as the bookmark name but does not add format, case sensitivity, or validation rules.

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?

Description clearly states verb 'remove', resource 'bookmark', and includes qualifier 'keeps paragraph content', distinguishing it from other bookmark-related tools like add_bookmark, list_bookmarks, and get_bookmarked_text.

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?

Implicit guidance that removal does not delete content, but no explicit when/why not to use or comparison with alternatives like delete_paragraph.

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