get_item_attachments

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

Annotations already supply the read-only, idempotent, non-destructive safety profile. The description adds useful behavioral context on top by specifying the return shape and enumerating the availability statuses. It doesn't discuss rate limits or auth, but for this simple read tool that is not a significant omission.

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?

Three sentences, front-loaded with the verb and object, and no filler. The use case, alternative, and return format each earn their 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?

The tool is simple, has a full output schema, and the annotations cover safety. The description goes beyond what is required by explaining the availability enum and pointing to get_pdf_content. It lacks an explicit definition of parent_key, but the name plus 'on a Zotero item' makes the tool callable.

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 only provides parent_key with type string and zero description coverage, so the description must compensate. It clarifies that the key refers to a Zotero item, but it does not specify the key's format or how to obtain it. For a single self-named parameter this is adequate but not rich.

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 names a specific action ('List file attachments'), a specific resource ('a Zotero item'), and a distinctive output dimension ('availability status'). It also explicitly contrasts with get_pdf_content, so an agent can distinguish this tool from its closest sibling without inspecting the schema.

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?

Gives explicit when-to-use guidance: 'Use this to check whether a paper HAS a PDF before fetching it.' It also names the alternative for a different task: 'to actually read the content, use get_pdf_content.' This is a clear decision rule.

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