index_pdf_library

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

With no annotations, the description fully assumes the transparency burden. It explicitly states reading PDFs, storing first 4000 characters, updating metadata, and being incremental. No contradictions, and the behavior is clear and complete for a non-destructive ingestion tool.

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 front-loaded with a one-line summary, followed by bullet-point-like lines detailing behavior and an Args section. Every sentence adds value, and the length is appropriate for the tool's complexity.

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 single parameter, lack of annotations, and presence of an output schema (which the description does not need to detail per rules), the description is comprehensive. It covers purpose, scope, behavior, and incremental nature. Minor gap: no mention of return value, but output schema likely covers it.

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 provides no parameter descriptions or enums, but the description adds complete meaning by defining the three scope options ('literature', 'zotero', 'all') and their corresponding directories. This fully compensates for the 0% 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 clearly states the tool extracts and indexes full text from PDFs in the Metis library, specifying specific directories (inputs/literature/ and Zotero storage). The verb 'extract and index' and resource 'PDFs in the Metis library' are precise. Among siblings like 'scan_literature' and 'index_library_pdfs', this tool's unique scope is evident.

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 notes the tool is incremental, processing only unindexed files, which implies it can be run repeatedly. However, it does not explicitly state when to use this tool over siblings like 'scan_literature' or 'index_library_pdfs', nor does it provide when-not-to-use scenarios.

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