Attach File

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description is not required to state safety. It adds useful nuance about authorization and stdio-only path restrictions, but does not disclose effects like overwriting existing attachments or specific permission requirements.

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 brief, front-loaded, and structured with an intro plus a terse Args list. Every sentence carries useful information with no filler.

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?

Given the moderate complexity of a 3-parameter attach operation, the description covers the core action, all parameters, and a key runtime constraint. It could be more complete with guidance on choosing between file and file_path, but overall it is sufficient.

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 Args section explains all three parameters clearly, including the OpenAI file object source and the restricted meaning of file_path. This significantly compensates for the minimal schema descriptions and provides actionable guidance beyond the bare input schema.

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 'Attach' and clearly identifies the resource (ChatGPT file input or authorized local file) and the target (an item). It is unambiguous but does not explicitly differentiate from sibling tools like save_pdf or download_pdf.

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 implies usage for attaching files to Zotero items and notes constraints on local file paths (stdio only unless HTTP roots enabled). However, it lacks explicit guidance on when to prefer this tool over alternatives or when not to use it.

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