add_linked_url_attachment

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

With no annotations, the description carries the full burden. It explicitly states the operation is an attachment, implying a mutating action. It doesn't disclose potential side effects like overwriting existing attachments, permission requirements, or error behavior, leaving room for improvement in behavioral detail.

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 three sentences, front-loaded with the primary action and followed by usage context. It contains no redundant information and each sentence contributes meaning.

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 six parameters and no output schema, the description covers the essential behavior and the main conditional path (parent_item). It doesn't address edge cases like invalid URLs or return values, but the comprehensive schema descriptions compensate, making it adequate for most use cases.

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 schema already documents all 6 parameters with clear descriptions, achieving 100% coverage. The tool description adds nuance by explaining that parent_item determines child vs standalone and that collections are only used for standalone attachments. This added context justifies a baseline 3 but not higher since the schema does most of the work.

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: 'Attach a linked URL to an existing Zotero item, or create a standalone linked-URL attachment.' It specifies a concrete action and resource, distinguishing it from sibling tools like add_items or import_pdf_to_zotero which handle different types of additions.

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: 'Use this to link external PDFs, web pages, or other resources to items already in your library.' It also explains the parent_item behavior for child vs standalone attachments. However, it doesn't explicitly name alternative tools or state when not to use this tool, stopping short of a 5.

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