bookmark_add

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

Since there are no annotations, the description carries the full burden of behavioral disclosure. It explicitly reveals the key non-obvious behavior: the tool updates title/tags rather than creating a duplicate when the URL exists. It does not cover details like tag merge semantics, but the most critical behavior is disclosed.

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 sentence with the main action front-loaded and the conditional update behavior in parentheses. There is no filler or redundant information.

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?

Adequate for a simple tool, but missing details such as what happens when tags are omitted during an update and whether the tool returns the created/updated bookmark. Without annotations or an output schema, more explicit behavioral context would be beneficial.

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?

With 0% schema description coverage, the description must compensate for parameter meaning. It adds that URL is the uniqueness key and title/tags are the updatable fields, but it does not explain the full semantics of the tags parameter, such as whether tags are replaced or appended.

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 adds a bookmark and immediately discloses the upsert behavior when the URL already exists. This distinguishes it from sibling tools like bookmark_delete, bookmark_search, and bookmark_list.

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 upsert note implies when the tool is appropriate (adding a new bookmark or updating an existing one), but no explicit guidance is given about alternatives or when not to use it. There is no reference to sibling tools such as bookmark_search or bookmark_list to help route the agent.

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