get_item_metadata

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

No annotations are provided, so the description must cover behavioral traits. It explains that it accepts item IDs or PDF paths and automatically finds parent items, which is useful. However, it does not disclose error handling, authentication needs, or any side effects of the operation.

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 concise with two sentences and an arguments line. It is front-loaded with the main purpose. It could be more structured (e.g., bullet points for args), but the current format is efficient and clear.

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?

Given that an output schema exists, the description does not need to explain return values. It covers the input types adequately and mentions key metadata fields. However, it omits information about error scenarios or prerequisites, which would enhance completeness.

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 single required parameter item_id has no schema description (0% coverage), but the description adds significant meaning: it specifies that the input can be a numeric itemID or a PDF file path, and that it works for both items and PDF attachments. This compensates well for the lack of schema-level documentation.

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 it retrieves complete metadata for a Zotero item, listing returned fields (title, authors, year, journal, DOI). It distinguishes from sibling tools like list_zotero_items and search_zotero_items by focusing on a single item's full metadata, but does not explicitly differentiate.

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 indicates it supports item IDs or PDF attachment IDs, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., search_zotero_items for multiple items). No exclusion criteria or context for optimal use are given.

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