create_campaign_folder

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

Although annotations exist (readOnlyHint, idempotentHint, destructiveHint all false), the description adds context: API key authentication, max 10 concurrent requests, and respect for read-only/dry-run modes. No contradiction.

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?

Description is 110 words, well-structured with clear sections: purpose, usage, auth/limits, args, returns. Front-loaded with key info, no wasted sentences.

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?

All parameters explained, usage guidelines provided, behavioral limitations stated, return fields described. Complete for a simple creation tool with 2 parameters and output schema present.

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 0%, but description fully compensates with detailed Args section: provides example values for name ('Q3 Newsletters'), explains account parameter linking to API key and default behavior, and references list_accounts. Adds significant 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?

Description clearly states it creates a folder to organize campaigns, with specific verb 'Create' and resource 'campaign folder'. Distinguishes from sibling tools like list_campaign_folders and update_campaign_folder by mentioning grouping and assigning campaigns via folder_id.

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?

Explicitly states when to use: to group related campaigns by client, month, or theme. Provides guidance on assigning campaigns and references list_campaign_folders for browsing. Lacks explicit when-not-to-use, but positive guidance is strong.

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