oncofiles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the multi-step process (walking folders, detecting changes, downloading, uploading, storing metadata) and the effect of parameters (dry_run for preview, enhance for AI processing). However, it doesn't mention potential side effects like rate limits, authentication requirements, or what happens with existing files, leaving some behavioral aspects uncovered.

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 appropriately sized and front-loaded with the core purpose in the first sentence. The workflow details are necessary for understanding the tool's behavior. The parameter explanations are concise and directly relevant. There's minimal wasted verbiage, though the structure could be slightly improved by separating the workflow description from parameter details more clearly.

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 (multi-step import process), no annotations, and the presence of an output schema (which handles return values), the description provides substantial context about the workflow and parameters. It covers the core behavior well but could benefit from mentioning prerequisites (like authentication setup) or potential limitations given the absence of annotations.

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?

With 0% schema description coverage and 2 parameters, the description fully compensates by clearly explaining both parameters: 'dry_run: Preview changes without importing' and 'enhance: Run AI summary/tag generation on new/changed files (default True)'. This adds essential meaning beyond the bare schema types, making the parameter purposes and effects completely clear.

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 specific action ('Import files from Google Drive into oncofiles') and resource ('files'), distinguishing it from siblings like 'sync_to_gdrive' (which presumably exports) and 'gdrive_sync' (which may be a different sync operation). It provides a detailed workflow explanation that makes the purpose unambiguous.

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 implies usage context through the workflow description ('Walks category/year-month subfolders...'), but does not explicitly state when to use this tool versus alternatives like 'gdrive_sync' or 'reconcile_gdrive'. It provides some guidance through parameter defaults but lacks explicit when/when-not instructions or named alternatives.

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