zotero_get_items_children

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

With no annotations, the description fully describes the behavior: it is a read operation (implied by 'fetch'), returns markdown sections grouped by parent, handles missing keys gracefully, and operates on the active library. It does not mention read-only explicitly but it's clear from context.

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 paragraph but is well-organized: purpose, comparison to sibling, parameter guidance, return format, error behavior, scope, and example. It is dense but not overly long, earning its place.

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?

Covers return format (markdown sections), error handling (per-item missing keys), scope, and relationship to sibling tool. Since an output schema exists, the description appropriately explains high-level return behavior without redundancy.

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 crucial details beyond the schema: specifies 8-character keys, allows JSON-encoded strings, and warns against concatenation. Schema coverage is 100%, but the extra context makes parameter usage unambiguous.

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 identifies this as a batch variant of zotero_get_item_children, specifying it fetches child items (attachments, notes, annotations) for multiple parent items. It distinguishes itself from the singular sibling tool by emphasizing the batch aspect.

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?

Explicitly advises using this tool when you have 2+ item keys for efficiency, and warns against passing a concatenated string. Mentions that missing keys are handled per-item and that scope is active library only, providing clear context for appropriate use.

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