delete_bookmark

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the destructive action ('remove'), but does not disclose side effects, idempotency, permissions, or error behavior. It is not misleading, and given the simplicity of the tool, the core behavior is adequately conveyed, but significant behavioral context is missing.

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: a single sentence plus a parameter explanation. Every word earns its place, and the purpose is front-loaded. There is no fluff or repetition, making it easy for an agent to parse quickly.

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?

The tool is simple (one required parameter) and an output schema exists, so the description does not need to explain return values. The description sufficiently covers the core purpose and parameter semantics for an agent to select and invoke the tool correctly in most cases. It lacks usage guidance and behavioral edge cases, but those are addressed in other dimensions, and for the tool's simplicity, this is nearly complete.

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 adds minimal value beyond the input schema. The schema already names the parameter 'tweet_id' and describes it as 'Tweet Id.' The description says 'The tweet ID to un-bookmark,' which essentially restates the parameter's name and the tool's purpose. It does not clarify the allowed integer/string ambiguity, format expectations, or how to obtain the ID, leaving the agent with the same information as the schema alone.

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 tool's function with a specific verb and resource: 'Remove a tweet from bookmarks.' This distinguishes it from sibling tools like bookmark_tweet (add) and get_bookmarks (list), and there is no ambiguity about its scope.

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 usage is implied by the purpose and the unambiguous name, but there is no explicit guidance about when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. It simply says 'Remove a tweet from bookmarks,' which inherently communicates when to use it, but does not proactively clarify edge cases or compare with related tools.

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