project_folder_create

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

With no annotations provided, the description must convey behavioral context. It only states the create action and location, without mentioning error conditions (e.g., duplicate folder names), permissions, or side effects. This is minimal and leaves the agent to assume standard 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?

The description is a single, direct sentence with no filler. It front-loads the action and location, making it easy to parse quickly.

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?

For a simple one-parameter create operation, the description covers the core action and location, and an output schema exists. However, it omits failure behavior (e.g., what happens if the folder already exists) and does not clarify the relationship to the current database folder navigation state, leaving minor gaps.

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 single parameter folder_name is fully documented in the schema with a description, so schema coverage is 100%. The tool description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 tool creates a folder in the current database folder, using a specific verb and resource. This distinguishes it from sibling tools like project_folder_list and media_pool_create_folder, which target different actions or locations.

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 phrase 'current database folder' provides implied context for when the tool is relevant, but there is no explicit guidance on when to use this tool versus alternatives such as media_pool_create_folder. No exclusions or alternative tool references are given, so usage is inferable but not explicit.

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