zotero_get_item_children

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

No annotations are provided, so the description carries full behavioral disclosure burden. It discloses return format (markdown), output shape for one vs. several keys, scope (active library only), and error-handling behavior (bad key reported separately vs aborting). It doesn't disclose rate limits or auth, but for a read-only list tool this is reasonably transparent.

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 dense but information-packed; every sentence adds value covering purpose, alternatives, batching rationale, output format, scope, and examples. It's slightly long but not padded — each clause serves a distinct purpose. The examples are useful and illustrative.

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 an output schema present, return-value documentation isn't required from the description. The tool has moderate complexity (single parameter, multiple accepted formats, batch mode), and the description covers purpose, use cases, alternatives, output shapes, error behavior, scope, and examples exhaustively. Nothing material is left undocumented.

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?

Schema coverage is 100% for the item_key parameter, establishing a baseline of 3. The description adds substantial value beyond the schema: it details the accepted formats (single key, array, JSON-encoded string), explains why batching matters (one round trip), defines what an 8-character key is, and provides two concrete usage examples. This exceeds the baseline.

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 has a specific verb+resource ('List the child items of parent Zotero items') and goes well beyond a generic statement by enumerating what child items include (attachments, notes, annotations under an attachment). It clearly distinguishes itself from sibling tools by explaining the output form (markdown, attachments/notes) and the scope (active library).

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 explicitly states when to use it ('to find an item's PDF/EPUB attachment key before zotero_create_annotation or zotero_get_pdf_outline'), names specific alternative tools that consume its output, and emphasizes batch usage ('Pass every key you have in ONE call'), explaining efficiency benefits over N round trips. It also notes error handling behavior for bad keys.

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