Attach Zotero link

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

Annotations already indicate this is a write operation (readOnlyHint false) and non-destructive (destructiveHint false). The description adds the v1 limitation that file-content uploads are not supported, which is useful context. It does not disclose other behavioral details such as whether URL validation occurs or how parent attachment linkage behaves.

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 short sentences with no filler. The core action is front-loaded, and the only additional sentence states an important limitation that 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?

For a write tool with no output schema and minimal annotation detail, the description establishes basic intent but omits essential parameter semantics such as what parentKey refers to or how the URL/title fields are used. An agent would need external knowledge to invoke this tool confidently and correctly.

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 the description provides no explanation of 'parentKey', 'url', or 'title'. The description does not compensate for the missing parameter schema documentation, leaving the meaning of required fields like 'parentKey' implicit and potentially ambiguous.

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 uses a specific verb and resource: 'Create a linked-URL attachment.' It clearly identifies what the tool does and distinguishes it from item/note/collection creation and from file-content uploads. The sibling list contains many creation tools, and this one is differentiated by its attachment-specific wording.

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 gives clear context that this tool is for linked-URL attachments and explicitly rules out file-content uploads in v1, which is a useful when-not boundary. It does not name an alternative tool or explain when to prefer siblings, but the exclusion is unambiguous.

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