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

The description indicates a mutating operation (set or clear) but provides no details on permissions, idempotency, or potential failures. Since annotations are minimal (only a title), more behavioral disclosure would be expected.

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 extraneous information. It is well-structured and easy to parse.

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 is adequate for a simple tool with no output schema, clearly communicating the action and target. It does not mention return values or errors, but that may not be necessary given the simple operation.

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 note parameter is well described ('Private note, or empty to clear'), but id has no description. At 50% schema coverage, the description does not fully compensate for the undocumented id, though id's purpose is relatively obvious.

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 (set or clear) and the target (private note on one saved item). It distinguishes from sibling tools like bookmarks_add or bookmarks_list by specifying 'on one saved item'.

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 implies it is for annotating an existing bookmark but does not explicitly contrast with alternative tools for adding or removing bookmarks. There is no direct guidance on when to choose this tool over siblings, but the phrase 'one saved item' provides some context.

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