works_folder_create

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

No annotations are present, so the description carries the full burden. It adds context about the delegated user's My Drive and the root-if-no-parent behavior, which is useful. However, it does not disclose potential side effects, permissions, or what happens when the user parameter is null, leaving gaps for a mutation tool.

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 sentence that is front-loaded with the action and resource, then adds the key scoping detail. Every word earns its place; it is appropriately concise.

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 simple create tool with no annotations and no output schema, the description provides the core purpose and a key location behavior. However, it omits return value information, prerequisites, and edge-case behavior, making it less complete for an agent that must invoke it correctly without additional context.

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?

With 0% schema description coverage, the description must compensate. It clarifies parent_folder_id via 'root if no parent' and references the user parameter via 'delegated user's My Drive', but it does not explain the name parameter or the optional nature of user beyond the schema default.

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 uses a specific verb ('Create') and resource ('folder'), and adds the scoping detail 'in the delegated user's My Drive (root if no parent)'. This clearly identifies the tool's function and distinguishes it from sibling tools like folder_enable/disable.

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 implies usage by stating the target location and the parent-folder behavior, but it does not explicitly say when to use this tool versus alternatives or provide any exclusions. It gives clear context but no alternative guidance, so it falls short of a 4.

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