get_items_details

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

With no annotations provided, the description discloses key behavioral traits: it accepts an array of keys, returns a key-to-metadata map, includes all type-specific fields, and defaults include_abstract to false for lightweight responses. This gives the agent a clear model of the tool's behavior without contradicting any annotations.

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 four concise sentences that front-load the core purpose, then cover input, alternative usage, return details, and parameter toggling. Every sentence contributes meaning with no redundancy or 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?

For a tool with 2 params and no output schema, the description covers the essential aspects: what it does, what it accepts, what it returns, and how parameters affect behavior. It even mentions type-specific fields and where to obtain item keys. Slight gap: no mention of error handling or invalid keys, but that's not critical for this use case.

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 already provides descriptions for both parameters (item_keys and include_abstract), achieving 100% coverage. The tool description adds some context (e.g., example sources for item_keys, rationale for include_abstract default), but it doesn't significantly extend beyond the schema's explanations, so a baseline score of 3 is appropriate.

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 opens with a specific verb+resource: 'Get metadata for multiple Zotero items in a single call.' It clearly distinguishes this from sibling tools like get_item_fulltext (which retrieves fulltext) and search_library (which searches) by focusing on batch metadata retrieval with a map return structure.

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 explicitly recommends using this tool when you need metadata for multiple items: 'Use this instead of calling get_item_details multiple times.' It also explains the include_abstract parameter's default behavior to guide when to enable it. However, it doesn't explicitly state when NOT to use it (e.g., for a single item), though that is implied.

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