drive_offline

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

No annotations are provided, so the description carries the full behavioral burden. It notes the effect happens 'on the phone' and that enable=false reverses the state, but says nothing about device connectivity requirements, storage cost, what happens to an already-offline file, or what the call returns.

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?

A single tight sentence with the action front-loaded and the mode toggle in a parenthetical. No wasted clauses, though the parenthetical breaks the flow slightly.

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?

With five parameters and none required, no annotations, and no output schema, the description should clarify how an item is identified (by name+path, or by index from a prior listing). It leaves that entirely unresolved, so an agent cannot tell a valid invocation from an invalid one.

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 100%, so the baseline is 3. The description only restates the enable flag that the schema already documents and adds nothing about how name, path, index, and occurrence combine to identify the target.

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?

States a concrete verb and resource: toggling a file's availability for offline use on the phone, with the enable flag spelled out for both directions. It does not distinguish itself from nearby siblings such as drive_download or drive_star, which also touch a file's state.

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?

Usage is only implied — the description implies 'use this when you want a file cached for offline access' but never says when to prefer it over drive_download or drive_star, nor any prerequisites (device connected, file exists).

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