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 behaviors: runs in background, returns immediately with status, imports/exports files with conflict resolution (GDrive wins), exports organized folders and metadata, and includes AI enhancement options. It lacks details on permissions, rate limits, or error handling, but covers most operational aspects well.

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 well-structured and front-loaded: the first sentence states the core purpose, followed by usage notes and a numbered list of actions. Every sentence adds value without redundancy, and the parameter explanations are brief yet informative, making it efficient and easy to parse.

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 (bidirectional sync with AI features), no annotations, and an output schema present (which reduces need to describe returns), the description is largely complete. It covers purpose, usage, behaviors, and parameters, but could benefit from more on prerequisites (e.g., auth setup) or error scenarios, though the output schema mitigates some gaps.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaningful semantics for both parameters: 'dry_run' is explained as 'Preview changes without syncing' and 'enhance' as 'Run AI summary/tag generation on new files (default True)'. This clarifies purpose beyond the bare schema, though it doesn't detail format or constraints.

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 with specific verbs ('Run full bidirectional Google Drive sync') and resource ('Google Drive'), distinguishing it from sibling tools like sync_from_gdrive and sync_to_gdrive by specifying bidirectional operation. It also mentions background execution and immediate return, adding operational context.

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 explicit usage guidance: it tells when to use this tool ('Run full bidirectional Google Drive sync') and when to use an alternative ('Use gdrive_sync_status to check progress and get the result when done'), clearly differentiating from the sibling tool gdrive_sync_status for monitoring purposes.

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