drive_cd

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 implies stateful navigation by saying "Enter a folder" and mentions returning the folder's items, but it does not disclose whether the current location persists, error conditions, permission requirements, or how the limit parameter affects returned items beyond what the schema already states.

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 a single, front-loaded sentence with no wasted wording. The parenthetical path rules are dense but each clause contributes useful navigation semantics.

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?

For a 3-optional-parameter navigation tool with no annotations and no output schema, the description covers the core path/index modes and says it returns the folder's items. However, "items" is vague without an output schema, and the stateful effect on the current location is only implied rather than explicitly stated.

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 baseline is 3. The description adds meaningful semantics beyond the schema by explaining path resolution: relative to current location, ".." means parent, and leading "/" means from My Drive; it also clarifies that index refers to the last list.

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 a specific verb and resource: "Enter a folder" via path or index and returns the folder's items. It is clear what the tool does, but it does not explicitly name sibling alternatives such as drive_up or drive_list to sharpen differentiation.

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 explains how to specify a path, including relative paths, ".." for parent, leading "/" for My Drive, and index from the last list. However, it does not explicitly say when to use this tool versus drive_up, drive_list, drive_open, or drive_location, nor does it provide exclusions.

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