meta_ads_split_tests_list

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

Declares 'Read-only' and lists return fields. Without annotations, it adequately conveys non-destructive behavior. Could mention pagination but sufficient.

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?

Two sentences, front-loaded with purpose and return fields, followed by read-only declaration and usage guidance. No filler.

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?

No output schema, but description lists specific return fields. Covers purpose, parameters, and usage flow. Complete for a list tool.

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%, but description adds context: account_id is optional with fallback, limit has default and max. Adds value 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?

The description clearly states it lists split tests (with internal API name) and specifies the returned fields, distinguishing from sibling tools like meta_ads_split_tests_get and meta_ads_split_tests_end.

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 this tool: 'Use this to find a study_id before pulling detailed results via meta_ads_split_tests_get or ending via meta_ads_split_tests_end.' Provides clear context and alternatives.

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