add_bookmark

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

No annotations are provided, so the description must convey behavioral traits. It mentions that bookmarks are for internal navigation and enforces a 'no spaces' constraint on bookmark_name, but does not disclose whether duplicate names are allowed, if the operation is undoable, or any side effects. This provides basic transparency but is not exhaustive.

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 concise, upfront about its purpose, and includes a structured Args/Returns section. Every sentence contributes value, with no redundant or irrelevant content.

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, the description adequately covers what it does, its parameters, and expected return. The mention of internal navigation adds useful context. However, it could specify uniqueness constraints or error conditions for added completeness.

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 input schema lacks parameter descriptions (0% coverage), but the description adds clarifying details: 'Index of the paragraph to bookmark' for paragraph_index, and 'Name for the bookmark (no spaces)' for bookmark_name. This adds meaningful context beyond what the schema provides.

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 action: 'Add a bookmark to a paragraph in the document.' It specifies the resource (bookmark) and the verb (add), and distinguishes this tool from siblings like 'list_bookmarks' or 'add_hyperlink_to_bookmark' by focusing on bookmark creation.

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 does not provide guidance on when to use this tool versus alternatives, such as when to use 'add_hyperlink_to_bookmark' instead. It lacks explicit context about prerequisites or exclusions, leaving the agent to infer usage from the tool's purpose alone.

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