oncofiles

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

No annotations are provided, so the description carries the full burden. It discloses the tool's behavior: scanning documents based on specific criteria and extracting metadata from cached OCR text. However, it lacks details on permissions needed, potential side effects (e.g., data modification), rate limits, or error handling, which are important for a tool that modifies data.

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 efficiently structured in three sentences: it states the purpose, explains the scanning criteria and extraction process, and provides usage context. Every sentence adds value without redundancy, making it front-loaded and concise.

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 complexity (batch metadata extraction), no annotations, and an output schema present, the description is mostly complete. It covers the what, why, and how, but could benefit from more behavioral details like safety or performance considerations. The output schema likely handles return values, so the description doesn't need to explain them.

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 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately explains the tool's operation without referencing parameters, meeting the baseline for parameterless tools.

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 purpose: to 'backfill structured_metadata for all documents that have AI summaries but no metadata' by scanning for documents with 'ai_processed_at' set but empty 'structured_metadata' and extracting metadata from cached OCR text. It specifies the exact conditions and mechanism, distinguishing it from siblings like 'extract_document_metadata' which likely handles individual documents.

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 clear context for when to use this tool: 'after adding the structured_metadata column to an existing database' and for documents with AI summaries but no metadata. However, it does not explicitly state when not to use it or name alternatives (e.g., 'extract_document_metadata'), though the context implies it's for batch processing.

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