get_attachment_file_path

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states the basic action and does not mention error conditions, permissions, prerequisites, or return value behavior. For example, it does not clarify whether the attachment must be a stored file or what happens if no file exists.

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 extremely concise: one sentence stating the purpose, followed by a clear parameter listing. It is front-loaded and contains no unnecessary words or repetition.

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 simple getter with one parameter and an output schema, the description is mostly adequate. However, it lacks important contextual details such as preconditions (e.g., attachment must be a file stored locally) and behavior for invalid or missing keys. These gaps could lead to misuse or confusion.

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 description adds meaningful context for the sole parameter item_key, explaining it as 'The attachment item's Zotero key.' This goes beyond the bare schema type 'string' and clarifies what the key refers to, which is essential for correct usage.

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: 'Get the local filesystem path of an attachment's file.' It specifies the verb ('Get') and the resource ('attachment's file'), and since sibling tools like get_bibliography or get_item_children have different purposes, it is well-distinguished.

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 does not explicitly state when to use this tool vs alternatives, but the purpose is specific enough that usage context is clear: it is for retrieving the local file path of an attachment. No exclusions or alternatives are mentioned, but this is acceptable for such a narrowly-scoped tool.

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