Get Zotero item notes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the 'Read-only' sentence adds no new behavioral information. The description doesn't disclose ordering, whether trashed notes are included, or what note metadata is returned.

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 short sentences with no unnecessary detail, and the main operation comes first. The redundant 'Read-only' sentence costs a point against a fully lean definition.

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?

For a one-parameter read-only tool with annotations covering safety, this is close to sufficient. It still lacks any explanation of the response shape or how the key relates to sibling lookup tools, leaving minor but real gaps.

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?

With 0% schema description coverage, the description must explain `key`, and it only does so indirectly by saying 'a Zotero item.' The parameter name plus that phrase suggest the key identifies an item, but no format or lookup guidance is provided.

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 phrase 'List note children for a Zotero item' identifies a specific verb and resource, and 'note children' distinguishes it from fetching the item itself. It doesn't name sibling tools like zotero_get_item or zotero_create_note, so it stops short of full differentiation.

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?

No explicit when-to-use or alternative guidance is given. The description implies the tool is for retrieving notes attached to a specific item, but doesn't say when to choose zotero_get_item or zotero_create_note instead.

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