ghl_ad_fb_audience_member_batch_update

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

The description aligns with annotations (readOnlyHint=false) by indicating a mutating operation. It adds context about using CSV or smart lists, but does not disclose additional behavioral traits such as rate limits, prerequisites, or what happens during partial failures. The idempotentHint=true annotation is not elaborated.

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 three lines: title, key functionality, and endpoint/OAuth scopes. It is efficient and front-loaded with the most important information. The inclusion of endpoint and OAuth details is somewhat extraneous for tool selection but does not detract significantly.

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 adequately outlines the purpose and input methods, but lacks details on expected output (no output schema) and concrete guidance on how to use CSV vs smart lists. Given the tool's moderate complexity, the description is acceptable but not comprehensive.

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 all parameters having descriptions and examples. The description mentions 'CSV or smart lists' which maps to csvPath and smartlistIds, but adds no new semantic meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 is a batch update for audience members, specifying add/remove operations via CSV or smart lists. The name and title reinforce this, and it is distinct from sibling tools like ghl_ad_fb_audience_member_add/remove which handle individual members.

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 mentions two input methods (CSV or smart lists), giving context for usage. However, it does not explicitly state when to prefer this batch tool over the individual add/remove sibling tools, nor does it provide exclusions or alternative recommendations.

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