delete_bookmark

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

Since no annotations are provided, the description fully discloses the soft-delete mechanism ('Archives the bookmark (soft delete via delete_at timestamp)') and the effect ('will no longer appear in the channel'). No contradictions or gaps.

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?

Description is concise (3 sentences + note), front-loaded with the core action, and every sentence adds value. No redundant information.

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 delete tool with 2 parameters and an output schema, the description is complete: it explains the action, behavior (soft delete), version/edition requirements, and effect on the UI. No missing information given the tool's complexity.

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?

Input schema covers both parameters with full descriptions (channel_id and bookmark_id). The description adds no additional parameter semantics beyond what the schema already provides, so baseline score of 3 is appropriate.

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 'Delete a channel bookmark' and explains soft-delete behavior. It distinguishes from sibling tools like update_bookmark and list_bookmarks by specifying the delete action and archival behavior.

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?

Includes edition requirements (Entry, Professional, Enterprise, Advanced) and minimum version (v10.1), explicitly excluding Team Edition. This provides clear context for when the tool is available. However, it does not explicitly compare to alternatives like update_bookmark or permanent delete, though soft-delete is noted.

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