zotero_get_attachments

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

Description explicitly states what it returns (filenames, paths, content types, link modes), which is valuable behavioral disclosure. Without annotations, it does not mention edge cases like empty results or authorization requirements, but for a simple read operation, this level of detail is reasonably transparent.

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?

One sentence, front-loaded with the action and resource, no filler. Every word adds value, making it a model of concise tool documentation.

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 one parameter, full schema coverage, and no output schema, the description is functionally complete: it states what the tool does and what data it returns. It lacks only minor details like behavior when no attachments exist, but these are not critical for basic usage.

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 coverage is 100%: the single 'key' parameter is already described with an example in the schema. The description adds only 'for a Zotero item', which does not materially enhance the schema's explanation. Baseline of 3 applies.

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 ('Get') and identifies the resource ('file attachments for a Zotero item'), clearly distinguishing it from sibling tools like zotero_get_item or zotero_get_notes. It also lists the outputs (filenames, paths, content types, link modes), making the tool's unique function explicit.

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 clearly implies when to use this tool: when you need file attachment metadata for a particular Zotero item. It does not mention alternatives or exclusion criteria, but the context is clear enough that an agent can infer it is meant for attachments rather than note or item metadata.

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