zotero_children

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the scope of the listing (child attachments/notes) but does not disclose behavior such as pagination, whether only immediate children are returned, or what happens for items without children. It provides some contextual value but not rich behavioral detail.

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, front-loaded sentence that uses the active verb 'List' and precisely communicates the tool's purpose with zero wasted words. It is appropriately concise and well-structured.

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 simplicity (one parameter, read-only, idempotent) and the presence of an output schema, the description provides sufficient information for an agent to invoke it correctly. It states the input (parent item key) and the output (child attachments/notes), and annotations cover the safety profile. The description is complete for a simple list operation.

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 schema defines `key` only as a string with no description (0% schema coverage). The description compensates by explaining that the key is a Zotero parent item key, giving semantic meaning to the parameter. It does not specify the exact key format, but for a single parameter this is sufficient to understand what to provide.

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 uses a specific verb 'List' and clearly identifies the resource: 'child attachments/notes for one Zotero parent item key.' This distinguishes it from sibling tools like zotero_item (which retrieves a single item) and zotero_collection_items (which lists items in a collection). The purpose is unambiguous.

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 does not explicitly mention when to use this tool versus alternatives, but the phrase 'for one Zotero parent item key' implies a prerequisite (you need a valid parent item key). No alternatives or exclusions are stated, so usage guidance is only implied rather than explicit.

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