create_folder

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

No annotations are provided, so the description carries full burden. It discloses important traits like Cloud server resolving parent segments and Data Center sending full path, plus naming restrictions. However, it lacks details on error handling, idempotency, or side effects when parent segments don't exist.

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 with no fluff. The first sentence states the purpose, and the second provides deployment-specific details. It is front-loaded and efficient.

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 has 3 parameters, one enum, and no output schema. The description covers purpose and parameter semantics for 'name' but omits return value information (e.g., folder ID) and does not explain the 'folder_type' parameter beyond schema. It lacks some completeness for a creation tool.

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%, so baseline is 3. The description adds value by explaining the 'name' parameter as a full folder path with examples and distinguishing Cloud vs. Data Center behavior, which goes beyond the schema's description.

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 Zephyr Scale' with a specific verb and resource. It distinguishes between Cloud and Data Center behaviors, and none of the sibling tools create folders, so it stands out clearly.

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 explicit guidance on when to use the tool (to create a folder) and explains deployment-specific path behavior. However, it does not explicitly state when not to use it or mention any alternative tools, though none exist in siblings.

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