zotero_get_item

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

With no annotations, the description carries the transparency burden. It discloses the key behavior of returning all fields including abstract, tags, collections, and CSL-JSON, which informs the agent of the output scope. It does not mention error cases or permissions, but for a read-only getter this is acceptable and adds value beyond the name.

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 two sentences, front-loaded with the action and resource, and each sentence earns its place. It is appropriately concise with no redundant phrasing.

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 simple single-parameter lookup with no output schema, the description provides sufficient context by naming the return content. It omits potential error conditions, but these are not mission-critical for a straightforward getter. Overall, it is complete for the tool's simplicity.

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 fully describes the single 'key' parameter with a type and example. The description's phrase 'by its key' merely restates the parameter, adding no new semantic detail. Since schema coverage is 100%, this meets the baseline of 3.

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 the verb 'Get', the resource 'full metadata for a Zotero item', and the scope 'by its key'. It distinguishes itself from sibling getters like zotero_get_notes and zotero_get_attachments by focusing on the item record itself and listing specific return fields.

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 context is clear: use this tool when you have an item key and need the complete metadata record. It does not explicitly mention alternatives or exclusions, but the 'by its key' phrasing and sibling tool names make the intended use obvious enough.

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