wafle_exports_meta_audience

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

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds behavioral detail about the output format (hashed email + phone per row, schema-compatible with Meta CSV) and filter usage, which is helpful beyond structured annotations.

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 concise sentences front-load the purpose and include meaningful use-case context without repetition or 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?

The description gives a solid overview of purpose and output format, but with no output schema and two undocumented parameters, it leaves the return type/delivery mechanism and the roles of since_ts/min_total_spent unspecified, making it only moderately 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 description coverage is 50%, and while the description enriches the 'segment' parameter by explaining its retargeting purpose, it does not provide meaning for 'since_ts' or 'min_total_spent', which lack schema descriptions. It partially compensates but leaves gaps.

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 the tool's function: exporting an audience formatted for Meta custom audiences with hashed email and phone, and mentions filtering by segment for retargeting cohorts. This distinguishes it from sibling exports like wafle_exports_google_ads and wafle_exports_customers.

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?

The description conveys the intended use case: building retargeting audiences for Meta custom audiences by filtering segment. It provides clear context, though it does not explicitly name alternatives or exclusions.

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