Zotero Get Notes

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

With no annotations provided, the description carries full behavioral disclosure. It describes case-insensitive substring matching, stripped-text vs raw HTML output, truncation behavior, limit capping, and the constraint that query and item_key cannot be combined. This is more than enough for an agent to predict side effects and output shape.

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 every sentence earns its place: core action, mode selection, parameter semantics, caveats, scope, and examples. It is front-loaded with the primary behavior and uses concrete examples to illustrate usage.

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 tool with five parameters, two main modes, an output schema, and important interaction constraints, the description is complete. It covers all parameter effects, mode limitations, scope behavior, and a practical example, so an agent has everything needed to invoke it correctly.

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 description coverage is 0%, so the description must document all parameters, and it does: limit (max results, default 20), query (search text), item_key (child notes scope), raw_html (original HTML for round-trip), and truncate (shortening long bodies). This adds meaning well beyond the bare schema.

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?

Description opens with a specific verb and resource: 'Read notes from the active Zotero library.' It clearly distinguishes two modes (list vs search) and child-note vs library-wide scoping, which separates it from sibling tools like zotero_get_annotations and zotero_manage_note.

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?

Provides explicit when-to-use guidance: 'Omit query to LIST notes... Pass query to SEARCH...' It also states when not to combine query and item_key, and points to zotero_manage_note for round-tripping raw HTML and zotero_switch_library for changing scope. An agent can select the right call mode without ambiguity.

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