index_pdf_library

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

With no annotations, the description carries the full burden. It discloses that the tool reads PDFs, stores only the first 4000 characters, updates the abstract, and is incremental (only processes unindexed files). This covers key behavioral traits without contradictions.

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 concise (four sentences plus an args list) and front-loaded with the main action. It is efficient but could be slightly tighter; nonetheless, it earns its keep.

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's simplicity (one parameter, no annotations, output schema exists), the description covers sources, storage location, incremental behavior, and scope. It does not need to explain return values due to output schema. Missing mention of performance or limitations, but overall adequate.

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 0% coverage (no descriptions for parameters). The description compensates by explaining the 'scope' parameter values: 'literature', 'zotero', and 'all', with clear mappings. This adds significant meaning beyond the schema.

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's action: 'Extract and index full text from all PDFs in the Metis library.' It specifies sources (inputs/literature/ and Zotero storage) and what is stored (first 4000 characters, updates abstract). This distinguishes it from siblings like 'search_literature' or 'scan_literature'.

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 provides context on when to use: for incremental indexing of PDFs, with scope options. It does not explicitly state when not to use or mention alternatives, but the purpose is clear enough for an agent to decide.

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