add_bookmark

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

With no annotations, the description partially discloses behavior: folder_path creates missing folders, defaults to 'Bookmarks bar', and top-level constraints. It does not mention behavior when both folder_path and parent_id are provided, or any authorization or rate limits. The additive nature is implied but not explicit.

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?

Three sentences that are front-loaded with the core action in the first sentence. Every sentence provides essential detail without redundancy. Efficient and well-structured.

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?

The description covers main usage but lacks details on return values, handling when both folder_path and parent_id are omitted (default behavior), conflict resolution, or output. Given the complexity (4 params, no output schema, many siblings), it is adequate but not comprehensive.

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 low (25%). The description adds meaning for folder_path (constraints, default, creation) and parent_id, but the required parameters url and title lack any description beyond the schema's type fields. The description does not fully compensate for the missing schema descriptions.

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 verb 'Add' and resource 'bookmark'. It distinguishes from siblings like create_folder by explicitly mentioning targeting a folder via folder_path or parent_id. The constraints on folder_path top-level names further specify the resource.

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 context on how to specify the target folder using folder_path or parent_id, and mentions the default folder. However, it does not give guidance on when not to use this tool or alternatives like update_bookmark. Explicit exclusions are missing.

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