zotero_get_item_children

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

No annotations are provided, so the description must carry the burden. It describes the return content in detail (highlights, colors, margin comments, notes), suggesting a read-only operation. However, it does not explicitly state it is non-destructive or mention any side effects, rate limits, or authentication needs.

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 every sentence adds value. No extraneous information.

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?

While the description explains the return content well, it omits critical context: the parameter 'item_key' is unexplained, and the output schema is not referenced. For a simple tool with 1 param, the description is incomplete.

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 input schema has 0% description coverage, and the description fails to explain the single required parameter 'item_key'. It does not provide any context on what it is or how to obtain it, leaving the agent without necessary information.

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 action ('Retrieve... annotations and notes') and the resource ('a paper'). It distinguishes from siblings by specifying the return of highlights with colors, margin comments, and notes. However, the tool name 'item_children' is broader than 'annotations and notes,' causing a slight mismatch.

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 a usage context ('Essential for literature_review prompt') but does not explicitly compare to siblings like zotero_search_annotations or specify when not to use this tool. The guidelines are implicit rather than direct.

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