zotero_match

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond the annotations by indicating that the tool performs fuzzy/near-exact matching and returns the 'best' match, which is not captured in structured metadata.

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 a single, front-loaded sentence with no redundant information. It states the core purpose in direct language without repeating schema or annotation details.

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?

With 6 parameters and a complex matching behavior, the one-sentence description is insufficient. It omits explanations of matching thresholds, candidate scanning limits, and the meaning of 'best'. The output schema helps with return values, but the description still fails to cover essential operational details.

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 only 17%, with only the 'query' parameter described. The tool description mentions 'title/DOI' which relates to the 'field' parameter, but fails to explain the roles of 'best', 'limit', 'threshold', and 'scan_limit'. The description does not compensate for the low schema coverage.

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 uses a specific verb ('Find'), names the resource ('Zotero item'), and specifies the matching basis ('exact or near-exact title/DOI'). This clearly distinguishes it from the sibling zotero_search, which likely performs broader searches.

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 implies the tool is for matching known titles or DOIs, but it does not explicitly state when to prefer this over zotero_search or mention alternatives. Usage context is present but not elaborated.

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