get-bookmark

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

With no annotations, the description should describe behavioral traits. It only states the action, omitting details such as whether the bookmark must exist, what happens if not found, and whether it is a read-only operation. This is insufficient.

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, front-loaded sentence. It is efficient and avoids unnecessary words. It is not overly verbose, though it lacks depth.

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 no output schema, the description should indicate return values or behavior, but it does not. It is minimal and does not address error conditions or the structure of the returned bookmark, leaving the agent with insufficient context.

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 coverage is 100% because the parameter bookmarkId has a description 'The bookmarkId to get.' The tool description does not add any additional meaning beyond what the input schema provides, so baseline 3 is appropriate.

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 'Get a bookmark by id.' clearly states the verb (Get) and the resource (bookmark by id). It distinguishes the tool from siblings like get-bookmark-content (which retrieves content) and search-bookmarks (which searches by criteria).

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 provides no guidance on when to use this tool versus alternatives. For example, it does not mention that it requires a known bookmarkId or that it is a simple read operation, unlike get-bookmarks-in-list or search-bookmarks which retrieve multiple items.

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