folder_create

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

Discloses key behaviors: returns persistent ID, triggers sync. Suggests calling sync_trigger after. No annotation contradictions. Could mention uniqueness constraints, but sufficient for a create operation.

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?

Four sentences covering purpose, optional nesting, negative guideline with alternative, return value and sync note. Includes examples. No wasted words.

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 2 parameters (both described), no output schema, and sibling tools, the description covers purpose, usage, parameters, return value, and sync behavior. Lacks only minor details like uniqueness, but overall complete.

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%, baseline 3. Description adds context: parentId is optional for root-level, get IDs from folder_list. Examples further clarify usage. Adds meaning beyond schema.

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 the verb 'Create' and resource 'a new folder in OmniFocus'. Distinguishes from sibling tools like folder_move by explicitly stating not to use this tool for moving.

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?

Provides explicit when-to-use (creating new folders, optionally nesting) and when-not-to-use (moving folders, prefer folder_move). Also gives context on obtaining parent IDs from folder_list.

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