List an item's notes and attachments

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

Annotations already mark the call as read-only and non-destructive. The description adds the return format ('Markdown list'), the nature of results ('child items with their own keys'), and their compatibility with sibling tools, giving behavior beyond the annotation flags without contradiction.

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 and divided into clear Args and Returns sections; every sentence contributes meaningful information and no content is repeated. The key resource and action are front-loaded in the first line.

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?

With a single parameter, read-only annotations, an output schema, and a description that covers input format, result nature, and downstream usage, the tool is fully specified for correct invocation. Nothing material is missing for an agent to use it effectively.

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?

Although the schema provides only the parameter name and type, the description explains that item_key must be an eight-character Zotero item key of the parent item. This fully compensates for the 0% schema description coverage and leaves no ambiguity about how to fill the single required argument.

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 states a specific verb and resource: 'List the notes and attachments belonging to an item.' This clearly distinguishes it from siblings like zotero_get_item (item details), zotero_get_collection_items (collection contents), and zotero_get_annotations (annotation list).

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?

It provides clear downstream context by noting the returned child keys are accepted by zotero_get_annotations and zotero_get_fulltext, implying this tool is the precursor for those calls. It stops short of explicitly stating when not to use it, but the intended workflow is clear.

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