Toggle a bookmark

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

The description explicitly states the action is a toggle, which is a key behavioral trait that changes state with repeated calls. The annotation only provides destructiveHint=false, so the description adds significant transparency about the side effect without contradicting anything.

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, using one sentence to convey the action, purpose, and toggling behavior. It is front-loaded and contains no unnecessary 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?

For a simple toggle operation with a single parameter, the description provides enough context to know how to call it. No output schema exists, and none is required for correct invocation. The purpose and state-changing nature are clearly communicated.

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 only parameter, thread_id, is not described in the schema. The tool description implies it references a 'discussion', so the meaning is inferable but not explicitly stated. Given the single parameter and obvious interpretation, it partially compensates for the lack of schema 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 states the verb 'Bookmark' and the resource 'a discussion', and the title adds 'Toggle' to clarify the action. It distinguishes this from sibling tools like list_bookmarks by indicating it modifies bookmark state rather than listing.

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 explains the purpose ('to return to later') and indicates the toggling behavior. However, it does not explicitly mention alternatives or when not to use it, such as when simply viewing bookmarks would suffice. Context is clear but lacks explicit exclusions.

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