edit_bookmarks

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

No annotations are present, so the description carries the full burden. It fails to clarify whether the provided bookmarks append to or completely replace the existing bookmark tree, and it does not mention that the output is written to a new file (per the 'output_name' schema parameter). This ambiguity is significant for a mutation tool.

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, focused sentence that conveys the core purpose without extraneous words. It is well-structured and immediately readable.

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 moderate complexity (nested bookmark objects, optional output naming), the description is too thin. It omits crucial behavioral details such as whether existing bookmarks are replaced or appended, and how the output file is handled. No output schema exists to compensate for this missing 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?

The schema provides complete descriptions for all parameters (100% coverage), including the 1-based page index and the default for output_name. The tool description adds no additional parameter-level details, so the baseline of 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 clearly states the action ('Add or replace'), the resource ('bookmarks'), and the target ('in a PDF'). It distinguishes itself from sibling tools like 'table_of_contents' (which extracts a TOC) by indicating a write operation, though it does not explicitly name any alternative.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention scenarios for adding vs. replacing bookmarks, nor does it reference sibling tools for comparison. The only sibling that could be confused is 'table_of_contents', but no explicit distinction is made.

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