create_folder

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'create' without addressing permissions, duplicate folder behavior, path handling, or side effects. For a mutation tool, this is a significant gap.

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 followed by a short, relevant example. It is front-loaded, contains no filler, and every word adds meaning.

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?

The tool is simple and the schema thoroughly documents all parameters, but the description lacks behavioral context such as what happens on duplicate folder names or what the output is. Since annotations are absent, the description could more fully clarify the operation's effects and success/failure outcomes.

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?

The schema covers all 3 parameters with descriptions (100% coverage), so the baseline is 3. The description adds minimal value beyond the schema, only illustrating folder_name via the 'images' example, and does not clarify path or site_id semantics further.

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 the specific verb 'Create' and clearly identifies the resource: 'a new folder in a website's storage.' This distinguishes it from sibling file operations like upload_file and delete_file. The example 'Create an images folder' reinforces the intended use.

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 gives an example use case ('Create an images folder') but no explicit guidance on when to use this tool versus alternatives. It implies usage for organizing website storage but does not mention exclusions or reference sibling tools like list_files.

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