workflow_attach_zotero_note

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

With no annotations provided, the description carries the full burden. It discloses the character limit (≤200 chars), the linking behavior to Obsidian, and the return format. However, it does not discuss error handling, side effects, or rate limits. It adequately covers the main behavioral traits but lacks depth.

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 concise and well-structured with distinct sections: one-sentence purpose, requirements, parameter list with helpful notes, and return format. Every sentence adds value without redundancy.

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 5 parameters, no output schema, and no annotations, the description is largely complete. It explains all parameters, return format, and prerequisites. Minor gaps include not clarifying what a 'child note' is in Zotero or constraints on the Obsidian link, but overall it provides sufficient context for an agent.

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 coverage is 0%, so the description must fully explain parameters. It does so effectively: item_key is '8-char Zotero internal key', citekey is 'Better BibTeX citekey for obsidian link', summary is 'one-sentence, ≤150 chars', rating defaults to '⭐⭐⭐', and cite_in is 'grant/paper section'. This adds substantial meaning beyond the schema's titles.

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 clearly states 'Create a short child note (≤200 chars) under the Zotero item that links back to the Obsidian deep note.' This is a specific verb+resource with scope (short child note, linking to Obsidian), and it distinguishes the tool from siblings like workflow_get_note and workflow_write_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?

The description mentions required environment variables (ZOTERO_API_KEY, ZOTERO_LIBRARY_ID) and lists arguments, which provides some usage context. However, it does not explicitly state when to use this tool versus alternatives (e.g., workflow_write_note for longer notes) or when not to use it.

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