Download a course file to disk

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

With readOnlyHint=true and openWorldHint=true already providing safety context, the description adds meaningful behavioral detail: the local side effect of saving, the return saved path, and special handling for Google-provided exports. There is no contradiction with the annotations - the description's behavior is read-only against the server while still having a client-side write.

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 three focused sentences, with the core action front-loaded and no filler. It efficiently covers the action, usage, and a special complication, each sentence earning its place.

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 5 params, complete schema coverage, and no output schema, the description fills important gaps: it explicitly states the return (saved path) and the non-Google/Google file behavior. It doesn't explain interactions between 'all' and 'fileName', but the schema describes both params, so the agent has enough context to call the tool correctly.

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 descriptions cover 100% of parameters, so the baseline is 3. The description mentions format's role for Google-export formats, but this only restates what that parameter describes in the schema. It does not add new parameter-level semantics beyond the schema, so no score above baseline.

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 states the core verb and resource ('Downloads a file from a content item and saves it locally') and the differentiator 'without extracting text' which separates it from text-reading siblings. It also covers a special case (Google-linked content items), making its 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?

It explicitly lists when to use the tool ('Use this for Office documents, images, archives, or anything the user wants to keep'), giving solid context. It doesn't name a specific alternative (e.g., bb_read_file) or state when not to use it, but the 'without extracting text' phrase implies the trade-off.

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