add

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

With no annotations, the description carries the full burden and does disclose two substantive behaviors: the target folder is auto-created if missing (a side effect), and the call is idempotent per-URL (skips duplicates). It omits permission/auth requirements and failure modes, but for a low-risk write it covers the non-obvious effects well.

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 short sentences, zero filler, with the core action front-loaded and the side effect and idempotency behavior following immediately. Every clause earns its place.

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, which the description correctly omits. However, the 0%-coverage input schema leaves 'title' unexplained in both places, and no sibling or usage context is provided for an ambiguously named 'add'. Adequate but with a real gap.

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 0% and no property carries a description, so the description must compensate. It implicitly explains 'folder' (created if missing) and 'url' (dedup key), but 'title' is never clarified at all, leaving one of three required parameters undefined. Partial compensation only.

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 pairs a specific verb with a specific resource ('Add a link to a folder') and qualifies the scope with parenthetical behavior. This distinguishes it from read/list siblings like read_this, tree, or search, though it never names an alternative. The generic name 'add' is rescued by the description, but sibling-level differentiation is left implicit.

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?

There is no when-to-use guidance and no mention of alternatives among a large sibling set that overlaps conceptually (note, save_group, snapshot, move). The only guidance-adjacent content is the dedup skip, which is behavior rather than selection criteria. An agent gets no help deciding this over, say, note or save_group.

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