get_library_stats

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

With no annotations, the description effectively conveys that the tool is a read-only query of library stats, taking no arguments and returning a formatted summary. It mentions potential dependence on Zotero sync but does not indicate any destructive actions. A slight improvement would be explicitly stating it does not modify the library.

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 well-structured with a brief introductory sentence, usage context, and a list of return values. It is informative without excessive length, though a minor reduction in detail about return values could improve conciseness.

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 tool has no parameters and an output schema is present, the description covers all necessary aspects: purpose, usage context, what it returns, and related tools. No gaps remain for an agent to effectively select and invoke the tool.

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 tool has zero parameters, so the baseline is 4. The description reinforces that it takes no arguments, which aligns with the empty input schema. No further parameter information is needed.

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 the tool summarizes the literature library, providing a quick overview of total papers, breakdown by source and item type, recent references, and Zotero sync state. It distinguishes itself from siblings like search_library and sync_zotero_library by focusing on summary statistics rather than searching or syncing.

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 advises using this tool before searching or citing to gauge the library's size and currency. It also mentions pairing with search_library and sync_zotero_library, indicating complementary tools. While it doesn't list specific scenarios to avoid, the guidance is clear enough for appropriate usage.

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