Create Subfolder

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, and the description adds real context on top: the exact permission scopes, the confirm=true gate, and the warning that the call 'may share access, notify people or incur provider charges.' Those side-effect disclosures are valuable and not derivable from annotations.

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?

Purpose and the positional detail are front-loaded in the first two sentences, followed by the permission block. The scope prose is somewhat repetitive across the three token variants, but each variant is a distinct usable path, so the length is largely earned.

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 7-parameter mutation with a nested payload object, no output schema and no annotations covering auth, the description supplies the missing permission and confirmation requirements plus side-effect warnings. It could still say what is returned or how name collisions are handled, but nothing needed to invoke it correctly is absent.

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 name, description, folder_id, payload, payload_file and account are each documented in the schema, including the mutual-exclusion rule between payload_file and body flags. The description adds nothing about how the body-flag, payload and payload_file paths relate, so the baseline 3 applies.

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 and resource ('Creates a new subfolder within a folder') and adds the ordering behavior ('next available position'). It implicitly separates itself from create_folder via the parent-folder framing, but never names a sibling tool, so an agent must infer the distinction.

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 concrete prerequisites: a token with 'Read, update & delete anything' or the delegated-permission scopes, and the hard requirement of confirm=true for the mutation. It stops short of stating when to prefer this over create_folder or copy_folder, so no explicit alternatives are offered.

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