create_folder

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

No annotations provided; description only states it creates a folder and returns id/name. Does not disclose side effects, error conditions (e.g., duplicate folder), permissions required, or whether it is idempotent. A creation tool should disclose more behavioral traits.

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?

Very concise and well-structured with Args and Returns sections. Every sentence adds value; no unnecessary information.

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?

Covers input parameters and return value adequately for a simple creation tool. However, missing behavioral context (e.g., error handling, permissions) reduces completeness. The output schema existence likely covers return structure, but description includes it anyway.

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?

Despite 0% schema description coverage, the description fully explains both parameters: name is display name, parent_folder_id explains default, and acceptable values (distinguished name or raw ID). Adds significant meaning beyond the schema types.

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?

Clearly states 'Create a new mail folder' with specific verb and resource. Distinguishes from sibling folder tools like delete_folder, rename_folder.

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 explains what the tool does but provides no guidance on when to use it versus alternatives, or any prerequisites. Usage context is implied.

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