delete_bookmark

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

No annotations are provided, so the description carries the full burden. It clearly implies a destructive write operation (deletion) and preconditions (slot must exist), which is appropriate for a delete tool. It does not disclose side effects (e.g., errors if slot doesn't exist), but the simplicity of the action makes this sufficient.

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, well-structured sentence that front-loads the action and includes a parenthetical source for the parameter. 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?

Given the tool's simplicity (one required param, no annotations, clear sibling context), the description is nearly complete. It lacks mention of the output schema, but the description's clarity on deletion outcomes suffices. An output schema exists but is not referenced, though that's acceptable for a delete operation.

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?

Schema description coverage is 0%, so the description must compensate. It explains that the 'slot' parameter should come from 'list_bookmarks', adding meaning beyond the bare integer type. This is concise and helpful for the agent.

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 it deletes a bookmark by slot number, with a specific verb ('delete') and resource ('bookmark'), and distinguishes from the sibling tool 'add_bookmark' by indicating deletion is done via slot number obtained from '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 explicitly tells the agent to get slot numbers from 'list_bookmarks' before using this tool, providing clear context. It does not, however, specify when not to use it or mention alternatives, but the sibling tools list includes other bookmark-related tools, so the instruction implicitly guides usage.

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