list_reference_fields

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

With no annotations present, the description carries the full burden and does it well: it explicitly labels the tool as read-only, discloses that broken field pairs are 'reported loudly', and explains that Mendeley/EndNote support is preservation-only with no insertion capability. This goes well beyond a basic summary of the operation.

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 clause adds value: scope, reported attributes, broken-pair behavior, preservation limitations, insertion alternative, and read-only status. It is front-loaded with the core action and includes no filler.

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 single-parameter read-only inventory tool with an output schema, the description covers scope, return intent, limitations, and error behavior. The only minor gap is the lack of explicit file_path semantics and absence of any direct comparison with integrity-specific sibling tools, but these are not critical 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 the only parameter, file_path, is not explicitly described. However, the tool's purpose is tied to inventorying fields in a document, making it clear that file_path targets the document to inspect. The meaning is inferable, but a direct mention of the parameter would have made it fully unambiguous.

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 ('Inventory') and names the exact resource (Zotero, EndNote, and Mendeley fields) plus the scope (body, footnotes, endnotes). It also enumerates what is reported, so an agent can distinguish it from broad tools like list_fields or integrity-specific tools like check_reference_field_integrity.

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 usage by stating what it inventories and notes that Zotero insertion exists via insert_zotero_citation, but it does not explicitly state when to prefer this tool over siblings like list_fields or check_reference_field_integrity. The preservation-only note gives some contextual guidance, but exclusions and alternatives are not fully spelled out.

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