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

Annotations already declare destructiveHint=true and idempotentHint=true; the description reinforces idempotency by explaining that request_key should be reused only for the same exact request, which is genuinely additive. It does not explain what the 'authorized directory' constraint means in practice, what happens on duplicate names, or any permission failure behavior.

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 short, front-loaded sentences with no filler; the core action is stated first and follow-up constraints come after. Slightly clipped phrasing ('this document home') costs a bit of clarity but nothing is wasted.

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?

An output schema exists so return values need no explanation, and the description covers the creation target, the nesting mechanism, the authorization source for workspace_id, and the idempotency contract. The only remaining gap is season_id, which is a parameter-level rather than description-level omission.

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 coverage is only 20% (just 'Folder name'), so the description does useful compensating work: it explains parent_folder_id as a nested-folder pointer, where workspace_id must come from, and the reuse semantics of request_key. However, season_id is completely unexplained in both the schema and the description, leaving one of five parameters opaque.

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 opens with a specific verb and resource ('Create a folder in this document home'), which tells an agent exactly what object is produced and where it lives. It does not explicitly distinguish itself from the similarly named siblings native.create_folder or native.create_document_folder, so differentiation relies on the 'document home' scope phrase.

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 gives procedural guidance for nesting ('Use a saved folder id for a nested folder') and for sourcing the workspace, but never states when this tool should be chosen over the sibling folder-creation tools. The guidance is about how to call it correctly rather than when to call it.

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