check_reference_field_integrity

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

With no annotations provided, the description carries the full burden, and it clearly discloses the operation is 'Read-only'. It also explains the ok flag behavior ('goes False on any broken or stray field marker') and the preservation-only behavior for EndNote and Mendeley, which goes beyond the schema and output schema.

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 front-loads the main action and output, then adds behavioral notes and a read-only declaration in a compact three-sentence structure. There is no filler or redundant restatement of the tool name.

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 integrity check with an output schema, the description supplies the needed context: when to run it, what managers are relevant, what the ok flag means, and preservation-only behavior. Nothing essential is missing.

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?

The schema has a single 'file_path' parameter with 0% description coverage. The description compensates by referring to 'a document containing Zotero, EndNote, or Mendeley citations', so the parameter's role is inferable. A score above 4 would require explicit path-format or edge-case info, which is not present.

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 verb ('Check') and resource ('reference-manager citations after an edit'), and further clarifies the exact output: 'counts by manager and kind plus an ok flag'. It names Zotero, EndNote, and Mendeley, which helps distinguish it from generic validation or citation-parity tools.

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 gives explicit usage timing ('Run it after editing a document containing Zotero, EndNote, or Mendeley citations') and adds preservation-only nuance for EndNote and Mendeley. It does not enumerate when not to use it or name sibling alternatives, but the provided context is clear enough to guide selection.

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