zotero_get_item_children

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

The description reveals that the tool returns PDF highlights with colors, margin comments, and standalone notes, providing good insight into the output. No annotations exist, but the description is sufficient for a read-only retrieval tool.

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 core purpose, and adds return details and context in the second sentence. No wasted words.

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?

With one required parameter and an output schema, the description covers the return types but fails to explain the input parameter. The output schema likely provides return structure, but the parameter gap reduces 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 description does not explain the 'item_key' parameter or how to obtain it. Schema description coverage is 0%, so the description should compensate, but it only vaguely mentions 'for a paper' without specifying the input format.

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 that the tool retrieves reading annotations and notes for a paper, listing specific return types (highlights, comments, notes). However, the tool name 'get_item_children' suggests broader functionality than just annotations, causing slight ambiguity.

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 mentions it's essential for a literature_review prompt, giving a use case. But it does not explicitly contrast with siblings like 'zotero_search_annotations' or state when not to use this tool.

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