colab_drive_project_dir

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

With no annotations, the description carries the full burden. It usefully discloses idempotent behavior ('Create (if missing)') and the Drive-mounted prerequisite, but says nothing about error behavior, permissions, or what the optional session parameter changes.

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?

Three sentences, front-loaded with the action and resulting path, zero wasted words. Format/path scaffolding is given up front where an agent needs it.

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?

The tool is simple, an output schema exists so return values need no explanation, and the description covers purpose, path, and prerequisite. The remaining gap is the undocumented 'session' parameter.

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% for two parameters. The description conveys what 'name' means by embedding it in the path template, but the optional 'session' parameter is never mentioned in either the description or the schema, leaving a real semantic gap.

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 specific verb+resource ('Create (if missing) and return a project folder') and even gives the exact path template. It is clearly distinguishable from Drive-management siblings, though it doesn't explicitly name an alternative tool for the same task.

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?

Gives clear context ('Use it for big datasets, checkpoints and results that must survive the session') and names the prerequisite by pointing to colab_drive_status. It stops short of explicit when-not guidance, but the usage context is well defined.

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