push_audience_suppression

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

No annotations are provided, so the description carries the full burden. It discloses that the action is logged to operator_action_log, and describes the two execution paths (forwarding to agent route with guardrail vs. queuing for manual approval). This provides good insight into behavioral traits beyond a simple mutation.

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 concise at 4-5 sentences, front-loaded with the primary action. It includes relevant details about logging and approval flows without being overly verbose. Slightly more could be trimmed, but it's well-structured.

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?

Given no output schema and 5 required parameters, the description covers purpose, behavior, and conditional execution. It does not describe return values or post-action confirmation, but for an action tool with clear context, this is adequate.

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 60%, and the description does not add significant meaning beyond the schema. The 'domains' parameter lacks description in both schema and description text. The description reiterates the platform enum and mentions rationale's purpose in the approval queue, but overall adds marginal value.

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 verb 'Add' and the resource 'audience exclusion list', specifying the goal to stop top-of-funnel ads for pipeline accounts. It distinguishes from sibling tools which are primarily read-oriented, making the purpose unambiguous.

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 explains when to use the tool: to suppress ads for accounts in open pipeline. It lists supported platforms and calls it a 'closed-loop action'. However, it does not explicitly state when not to use or provide alternatives to other similar tools, though the context is still clear.

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