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. It only states the action without disclosing behavior such as whether intermediate directories are created, what happens if the folder already exists, or any permission requirements. This is a minimal statement that lacks critical behavioral context.

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 that states exactly what the tool does with no redundant words. It is front-loaded with the verb and resource, making it highly concise and effective.

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 with one well-documented parameter, but the description lacks behavioral details like error handling or side effects. The path example implies nested folder creation, but the description itself does not clarify this. It is minimally adequate for basic use but not comprehensive for edge 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?

The input schema provides 100% coverage for the single 'path' parameter, including an example. The description adds no additional parameter information. Per the rubric, high schema coverage yields a baseline of 3, and the description does not exceed that.

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 'Create a new folder in Nextcloud' with a specific verb and resource, making it unambiguous what the tool does. It distinguishes itself from sibling create tools by specifying 'folder' in 'Nextcloud', so an agent can easily select it.

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 clear context: use this when you need to create a folder in Nextcloud. It does not explicitly mention alternatives or exclusions, but the name and resource make the use case obvious. This meets the 'clear context, no exclusions' criterion.

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