update_audience

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

The description discloses the two-phase dry_run/confirmed workflow and provides an example, adding meaningful behavioral context beyond the schema. No annotations exist to contradict.

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?

Three concise sentences: purpose+endpoint, Dto field summary, workflow with example. No wasted words, front-loaded.

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?

Adequately covers parameters and workflow for the tool's complexity (8 params, two-phase commit). Lacks return value description but no output schema exists. Reasonably 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?

Despite low schema coverage (38%), the description maps to most parameters, explains condition_match_mode requirement when conditions non-empty, and illustrates the dry_run/confirmed order. This compensates for the schema 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 updates an audience (user list), provides the HTTP PATCH endpoint, and differentiates from sibling update tools targeting other resources like triggers or project tiers.

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 explicit guidance on when to use this tool versus alternatives (e.g., other update tools); lacks when-not-to-use or prerequisites like requiring an existing audience.

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