add_child_note

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

Discloses write operation, need to close Zotero, and refresh requirement. No annotations provided, so description bears full burden and does well.

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?

Well-structured with separate sections (description, note, Args). Could be slightly more concise, but every sentence adds value.

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 purpose, parameters, post-usage steps, and behavioral notes. Output schema is present but description is self-sufficient for a simple 2-param tool.

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?

Adds meaning beyond schema: describes parent_item_id as numeric string representing item ID, and note_content as HTML/plain text with Markdown support. Schema had 0% coverage, so this is essential.

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?

Clearly states creating child notes for Zotero items, a specific verb+resource. Distinguishes from sibling tools like batch_annotate or create_pdf_annotation.

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 post-write refresh requirement and note about needing to close Zotero. Lacks comparison to sibling tools but gives clear context for usage.

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