outlook_create_folder

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

No annotations are provided, so the description must carry the full burden. It mentions that 'parent_folder' can be a name or ID for nesting, but fails to disclose any behavioral traits such as permissions required, error behavior if parent_folder does not exist, or the effect on existing folders. This is insufficient for a mutation tool.

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 efficiently conveys the core purpose and a key nuance (nesting). Every word is necessary; no redundancy.

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?

Given the tool has only two parameters, no output schema, and no annotations, the description covers the primary purpose and the main optional feature (nesting). It is mostly complete, though it could mention that folder names must be unique or what happens on success.

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 description coverage is 0%, so the description must compensate. It explains that 'parent_folder' is for nesting under an existing folder and can be a name or ID, adding meaning beyond the schema. However, it does not elaborate on the 'name' parameter or restrictions like uniqueness. Adds value but not exhaustive.

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 a clear verb 'Create' and specific resource 'mail folder', and distinguishes from sibling tools like 'rename_folder' or 'delete_folder' by stating exactly what it does.

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 implies usage for creating folders with optional nesting, but does not explicitly state when to use this tool versus alternatives like 'outlook_rename_folder' or 'outlook_delete_folder'. No when-not or exclusion guidance is given.

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