create_folder

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

No annotations provided, so description carries full burden. Fails to disclose critical mutation behaviors: idempotency (error vs success if exists), auto-create intermediate directories (mkdir -p behavior), or required permissions. Only states the action occurs, not how it behaves.

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?

Extremely concise six-word sentence with zero redundancy. Front-loaded action verb immediately communicates intent without superfluous language.

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?

Adequate for low complexity (single parameter, no output schema), but lacks behavioral context expected for a mutation operation. Missing error conditions and side-effects that would help an agent handle failure cases.

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 100% with path parameter fully documented. Description adds no additional semantics beyond schema (e.g., path normalization rules, trailing slash handling, case sensitivity), warranting baseline score.

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 specific verb (Create), resource (folder), and scope (Dropbox) clearly. Distinguishes from siblings like delete, move, and list by operation type, though could better differentiate from create_shared_link beyond implied resource name.

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?

Provides no guidance on when to use versus alternatives (e.g., move/copy for existing folders), prerequisites like parent folder existence, or behavior if the folder already exists.

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