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 key traits: idempotency (checks existing folders), handling of bilingual/legacy names (renames old), and patient-type logic (oncology/general folder skipping). It does not cover permissions, error handling, or rate limits, but provides substantial operational context beyond basic function.

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: a clear purpose statement followed by behavioral details and parameter explanation. Every sentence adds value—no redundancy or fluff. It is front-loaded with the main action and remains focused throughout.

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 (patient-type logic, idempotency) and the presence of an output schema (which handles return values), the description is complete. It covers purpose, behavior, and parameter semantics adequately, with no annotations to rely on. The output schema likely details the created structure, so the description need not explain return values.

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% description coverage for its single parameter, but the description compensates fully by explaining 'root_folder_id' as 'The Google Drive folder ID to create subfolders in.' This adds essential meaning beyond the bare schema, clarifying the parameter's role and format expectation, which is critical given the low 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 specific action ('Create the folder structure') and resource ('in a GDrive root folder'), with additional specificity about being 'patient-type-aware'. It distinguishes itself from sibling tools like 'gdrive_set_folder' or 'gdrive_sync' by focusing on structured folder creation rather than general folder operations or synchronization.

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: when setting up a patient-type-aware folder structure in a Google Drive root folder. It implicitly suggests alternatives by mentioning specific behaviors (e.g., oncology vs. general patients), but does not explicitly name when not to use it or list alternative tools like 'gdrive_set_folder' for simpler folder operations.

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