ad_manager_fb_batch_update_audience_members

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

Annotations already indicate it is a write operation (readOnlyHint=false), not destructive (destructiveHint=false), and idempotent (idempotentHint=true). The description adds no behavioral context beyond that, such as side effects, authentication requirements, rate limits, or what happens to existing members. While the annotations cover the safety profile, the description could elaborate on the nature of the update (e.g., additive, replacing) but does not. This meets the baseline but adds no extra value.

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 a single concise sentence: 'Batch update audience members'. It is front-loaded with the action and resource, with no filler. It is appropriately sized for what it conveys, though it is minimal. It earns a 4 for efficiency, though it sacrifices completeness.

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?

With 6 parameters (2 required) and no output schema, the description is critically insufficient. It provides no explanation of the operation types (e.g., add, remove, replace), the role of csvPath, smartlistIds, dynamicAudience, or how the batch process works. An agent cannot infer the correct usage beyond the parameter names, which are not self-explanatory. This is a significant gap for a tool that appears to have complex business logic.

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%, so all parameters have descriptions. However, these descriptions are terse (e.g., 'Batch operation type', 'CSV file path', 'Smartlist IDs array'). The tool description does not add any further meaning about how these parameters interact or which are required for which operation. Since the schema already documents the parameters, the description adds no additional semantics, warranting the baseline 3.

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 states the action 'update' and resource 'audience members', which is specific. It suggests a batch operation, distinguishing it from single-member tools like ad_manager_fb_add_custom_audience_member or ad_manager_fb_remove_custom_audience_member. However, it does not clarify whether the update is adding, removing, or replacing members, nor does it mention the operationType parameter, so it is clear but not fully specific.

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. There is no mention of when to use it instead of the add/remove single-member tools, or the update_custom_audience tool. An agent would have to infer from the name and parameters alone, which is insufficient.

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