twitter_unbookmark_tweet

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that it requires write capability, which aligns with the behavior. No contradictions; the description reinforces the mutation nature without adding extensive new behavioral context.

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?

Two sentences: first states action, second clarifies input and permission. No redundant information, every word earns its place.

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?

No output schema, but the action is straightforward (delete bookmark). The description gives enough context for an agent to understand input requirements and permission. Minor gap: could mention return structure, but not critical for this simple write 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 100%, so baseline is 3. The description mentions providing tweet id or url, but does not add significant meaning beyond what schema parameters already provide (each has a description).

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 specifies the action ('remove a tweet from bookmarks') and the resource ('tweet from YOUR authenticated account's bookmarks'). It distinguishes itself from siblings like twitter_bookmark_tweet (add) and twitter_bookmarks (list) by focusing on removal.

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 indicates when to use the tool (to unbookmark a tweet) and mentions the prerequisite ('requires write capability'). It does not explicitly state when not to use or list alternatives, but the sibling tools provide implicit contrast.

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