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

Adds real behavior beyond the annotations: extraction and enrichment run asynchronously after the save, and a replayed id returns the existing item rather than creating a duplicate. This explains a concrete idempotency contract and post-call timing that the idempotentHint/openWorldHint flags alone do not convey.

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?

Two sentences, zero filler, front-loaded with the core action and the usage trigger before the id/idempotency mechanics. Every clause carries operative information.

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?

An output schema exists, so return values need not be described. Between the usage trigger, async enrichment note, and id-reuse rule, an agent has everything needed to invoke and safely retry this tool.

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 both parameters are already documented in the schema (including the UUID-retry rule). The description mostly restates that guidance, adding only 'no lookup needed'; the baseline of 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Save an HTTP or HTTPS web page URL into the user's Sensefold library'), which implicitly separates it from save_note by scoping to web page URLs. It does not explicitly name a sibling, but the URL-type restriction is precise enough to route correctly.

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?

Gives a clear trigger: 'Use when the user asks to save, clip, or bookmark a link.' It does not state exclusions or explicitly point to save_note for non-URL content, so the when-not guidance is left to inference.

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