create_folder

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

With no annotations, the description must disclose behavior. It explains that parent_path can be created if missing and lists valid root folders. However, it omits details on handling conflicts (e.g., both identifiers provided), duplicate names, or return value.

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 two sentences, concise and well-structured. Every line adds value without redundancy. It is appropriately sized for the tool's complexity.

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?

Given 3 parameters, no output schema, and no annotations, the description covers key usage but lacks details on return value, error handling (e.g., duplicate names), and behavior when parent_path already exists. More completeness would improve agent confidence.

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 0%, so the description compensates by explaining parent_path (default, creation behavior, valid top-levels) and mentioning parent_id. However, 'name' lacks constraints, and 'parent_id' format is unspecified, leaving some ambiguity.

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 clearly states the action 'Create a folder' and specifies the resource. It distinguishes from siblings like 'add_bookmark' by focusing on folder creation. The default path and valid top-level folders are mentioned, making the purpose unambiguous.

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 provides guidance on using parent_path vs parent_id, including default behavior and valid top-level folders. However, it does not explicitly state when to prefer this tool over 'ensure_folder_path', which might be used for creating entire folder paths.

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