Remove Bookmark

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

The description correctly indicates a destructive action, matching the destructiveHint annotation. However, it adds no further behavioral context (e.g., permanent deletion, impact on other objects, required permissions). Annotations already cover destructiveness, so the description adds minimal value.

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 a single, front-loaded sentence with no unnecessary words. It is appropriately concise for a straightforward tool.

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 deletion tool, the description is adequate but lacks completeness: it does not mention the absence of undo, confirmation, or error handling. While the single parameter is clear, additional context on the tool's finality would be helpful.

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?

The description mentions the parameter 'by its ID' but does not add details beyond the schema (e.g., format, examples, constraints). With schema coverage at 0%, the description should compensate but fails to do so meaningfully.

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 (spatial bookmark), and the method (by its ID). It distinguishes from sibling tools like add_bookmark and get_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 removal by ID but does not explicitly state when to use this tool versus alternatives (e.g., batch deletion, conditional removal). No 'when not to use' guidance is provided.

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