create_item_manual

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

The description discloses the duplicate-checking behavior, which is not expressed in the annotations. It also clarifies that metadata is manually supplied rather than resolved. This goes beyond the readOnly/openWorld annotations without contradicting them.

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?

Three short sentences: purpose first, usage condition second, duplicate check third. Every sentence adds distinct value and there is no redundant phrasing.

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?

The description is sufficient for tool selection: purpose, alternative, and a key behavior are present. However, the tool has 15 parameters and no schema description coverage, so an agent still lacks crucial input-format guidance for non-obvious fields, making the overall definition incomplete for correct invocation.

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% and there are 15 parameters, so the description carries the burden of explaining parameter meaning. It does not describe any specific parameter or format, leaving complex fields like creators, tags, and collection_keys undocumented in prose.

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 states a specific action and resource ('Create a Zotero item') and clearly differentiates itself from the sibling create_item by emphasizing manually provided metadata instead of resolving a DOI/URL. An agent can immediately understand what this tool does and how it differs.

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 explicitly tells the agent when to use this tool ('Use this instead of create_item when you have structured metadata already') and names the alternative. It also adds a relevant behavioral condition ('Checks for duplicates') that helps with selection.

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