Get item children

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool's safety profile is known. The description adds a useful behavioral/data expectation: attachment children include linkMode and filename needed by downstream tools. It does not disclose potential pagination, error, or API-specific behavior beyond what the schema and annotations cover.

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?

Two focused sentences with no filler. The first sentence states the core purpose immediately, and the second adds high-value information about downstream consumers of the returned attachment fields. Every sentence earns 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?

Given the presence of an output schema and complete parameter documentation, the description does not need to enumerate return fields. It provides enough context about what the tool returns and how it connects to sibling tools. The only missing element is explicit guidance about choosing this tool over alternatives, which is already reflected in the usage_guidelines score.

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?

All five parameters are fully documented in the input schema, including defaults, ranges, patterns, and usage notes like 'Omit for the personal library.' The description adds no parameter-level semantics; its mention of linkMode and filename relates to returned attachment data rather than to input parameters.

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 names a specific operation: 'List the child notes, attachments and annotations of an item.' This clearly identifies the resource (item children), the action (listing), and the content scope, making it easy to distinguish from siblings like zotero_get_item or zotero_get_item_fulltext.

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 implies when to use the tool: when you need child notes, attachments, or annotations of an item. It also usefully indicates that attachment children carry data needed by zotero_get_attachment_path and zotero_get_item_fulltext. However, it provides no explicit exclusions or alternatives for when a different tool should be used instead.

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