Create Ad Label

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

All annotations are false, offering little behavioral context. The description only states that it creates a label and does not disclose whether duplicate labels are allowed, what side effects occur, or what authorization is needed, beyond the obvious write 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?

The description is short and front-loaded with a one-sentence purpose followed by a succinct argument list. Every line serves a purpose, and no unnecessary details are included.

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?

For a simple create operation, the description covers the object and both required parameters, but it omits return value details, behavior on duplicate names, and expected output. An agent could likely use it minimally, but more context would be needed to handle edge cases confidently.

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 only 33% (only response_format is documented), yet the description merely restates parameter names: 'ad_account_id (string): Ad account ID' and 'name (string): Label name.' This adds minimal meaning beyond the schema and lacks format constraints, examples, or parameter relationships.

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 the specific verb 'Creates' and identifies the resource as 'a label for organizing ads, ad sets, or campaigns.' This clearly distinguishes it from sibling tools like meta_create_ad or meta_create_ad_rule, since the object is a label rather than an ad or rule.

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?

No guidance is provided on when to use this tool versus alternatives, such as meta_list_ad_labels to read existing labels or meta_create_ad_rule for rule creation. There are no prerequisites, caveats, or preferred scenarios described.

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