Update bookmark

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

With no annotations provided, the description carries the full behavioral disclosure burden. It reveals that only the title is changed and position is immutable. However, it does not disclose potential errors (e.g., non-existent bookmark), permission requirements, or side effects.

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 two declarative sentences with no wasted words. The primary action is front-loaded, and the limitation is given immediately afterward.

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 rename tool with 3 parameters and no output schema, the description adequately covers what the tool does and its main constraint. It is complete enough for an agent to invoke correctly, though it omits details like validation or return value.

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 does not add meaning beyond the schema; it refers to 'at a given position' which maps to the 'time' parameter, but does not elaborate on format or constraints of other parameters.

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 renames the bookmark at a given position, and explicitly notes that the position cannot be changed. This distinguishes it from siblings like delete_bookmark and create_bookmark.

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 explicit guidance: if the position needs to change, delete and re-create instead. It implies alternatives (delete_bookmark, create_bookmark) but does not name them directly. No guidance on other tool usage contexts.

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