get_item

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves 'detailed metadata,' implying a read-only operation, but doesn't cover aspects like authentication requirements, rate limits, error handling, or what 'detailed' entails. This leaves significant gaps in understanding the tool's behavior beyond its basic purpose.

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 a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded with the core action and resource, making it easy to parse and understand quickly, which is ideal for conciseness.

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 the tool's low complexity (2 parameters, no nested objects) and the presence of an output schema (which handles return values), the description is minimally adequate. However, it lacks behavioral details (e.g., error cases, permissions) and parameter guidance, making it incomplete for optimal agent use, though not severely deficient due to the simple structure.

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 description adds no semantic information about the parameters beyond what the input schema provides. With 0% schema description coverage, the parameters 'item_key' and 'format' are undocumented in both the schema and description. However, the baseline is 3 because the tool has only 2 parameters, and the description implies retrieval of a single item, which loosely relates to 'item_key,' but it doesn't compensate for the lack of details on parameter usage or meaning.

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 tool's purpose with a specific verb ('Get') and resource ('detailed metadata for a single Zotero item'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'search_items' or 'get_collection_items', which might also retrieve item information but with different scopes or filters.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an item key), exclusions, or comparisons to siblings like 'search_items' for broader queries or 'get_collection_items' for collection-specific lists, leaving the agent to infer usage context.

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