zotero_attach_link

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently states that this creates a URL link attachment rather than a file and discloses the limitation that file uploads are unsupported. It does not cover permissions or irreversibility, but for a simple attachment operation, this is adequate context.

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 two sentences long, front-loaded with the primary purpose, and every word adds value. It avoids fluff and is well-structured for quick comprehension.

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, especially since an output schema exists to cover return values. However, the lack of explicit parameter guidance for 'title' and the minimal schema descriptions leave a small gap. Overall, it covers the essential action and limitations sufficiently, but not perfectly.

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 no parameter descriptions (0% coverage), so the description must compensate. It implicitly clarifies that 'url' is a web link (URL) and 'parent_item_key' refers to a reference, but it does not explain the 'title' parameter. This partial coverage leaves a gap for one of the three parameters.

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's function with a specific verb and resource: 'Attach a web link to a reference.' It also distinguishes itself from file uploads by explicitly saying it creates a link attachment, not an uploaded file, which differentiates it from potential siblings.

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 clear context for when to use the tool (attaching web links) and when not to (uploading files). It explicitly states that file uploads are not supported and advises dragging files into Zotero directly, effectively giving a when-not-to-use. It does not name an alternative tool, but the guidance is clear.

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