Prepare & Hash Custom Audience Payload

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

The description discloses meaningful behavioral details beyond basic operation: emails are trimmed and lowercased, phones are normalized to E.164, hashing uses SHA-256, and uploading is optional. With no annotations available, this is a strong attempt to describe side effects and transformations, though it does not cover all consequences such as removal behavior or return values.

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 two tightly written sentences with the core transformation front-loaded and the conditional side-effect clearly stated afterward. There is no filler or redundancy.

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 provides the essential transformation and optional upload capability, which is adequate for a moderately complex tool. However, with no output schema and no annotations, it omits return behavior and explicit selection criteria relative to overlapping siblings, leaving some context for the agent to infer.

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 100%, so the baseline is 3. The description reinforces the normalization behavior and optional upload, but it adds little semantic meaning beyond what the input schema already documents for each parameter.

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 a specific operation: normalizing raw emails and phone numbers into SHA-256 hashes, with optional direct upload to a custom audience. This clearly identifies the tool's resource and action, though it doesn't explicitly differentiate itself from sibling tools like mutate_audience_membership.

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 about when to use this tool versus alternatives such as mutate_audience_membership or other custom-audience tools. The optional upload behavior creates overlap with mutation tools, but the description never says use this for raw PII or use mutate_audience_membership for already-hashed members.

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