create_bookmark

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

The description only says 'Create a new bookmark in linkding,' which essentially restates the tool name. It discloses no behavioral traits such as authentication needs, auto-scraping behavior, or what happens on success or failure. With no annotations provided, the description carries the full burden, and it fails to meet it.

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 with no extra words or repetition. It is front-loaded and easy to parse, earning a perfect score for conciseness.

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 tool with 9 parameters and an output schema, the description is far too minimal. It does not explain the bookmarking workflow, potential side effects like automatic title/description scraping, or how the response is structured. While the schema covers parameter details, the overall context of the tool's behavior is missing, making it incomplete for an agent to use effectively.

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 input schema has 100% description coverage for all 9 parameters, so the schema already provides full meaning. The description adds no parameter-specific information, but per the rubric, the baseline is 3 when schema coverage is high, and it does not need to repeat what is in the schema.

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 creates a bookmark in linkding, using a specific verb and resource, and it is distinct from sibling tools like update_bookmark or delete_bookmark. However, it adds little beyond the tool name and does not elaborate on the bookmark's purpose or unique characteristics.

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, such as whether to use it for new bookmarks only or if other tools handle edge cases. It does not mention prerequisites or exclusions, leaving the agent without contextual decision-making help.

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