meta_ads_split_tests_create

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

Describes mutability ('reversible via rollback_apply'), test mechanism (duration, objective comparison), and cell requirements. Lacks permission or rate limit info, but with no annotations, it covers key behavioral aspects well.

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?

Five sentences, front-loaded with action and return value. Each sentence adds unique, useful information without 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?

Covers main purpose, return, mutability, prerequisites, and test mechanics. Lacks error handling or rate limits, but for a creation tool with no output schema, it is fairly 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% with good descriptions. Description adds value by explaining cell prerequisites, rollback behavior, and default confidence level, which are not in the 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 'Creates a new Split Test' and returns 'study_id'. Distinguishes from siblings by mentioning rollback_apply and referencing meta_ads_split_tests_get for analysis.

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 clear prerequisites ('cells must reference pre-existing ad sets') and post-analysis guidance ('use meta_ads_split_tests_get'). Could be more explicit about when to use versus other split test tools, but still good context.

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