upload_customer_match_data

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says 'upload' without explaining side effects (e.g., whether data is merged or overwritten), required data hashing format, or any validation or response behavior. This is a significant gap for a mutation tool.

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, front-loaded sentence that efficiently states the core action. No wasted words; it earns its place while remaining appropriately terse.

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 tool is a data upload operation with no annotations and no output schema. The description fails to provide essential context such as prerequisites (list must exist), data formatting requirements (hashed identifiers), or what happens to existing list data. This leaves the agent underinformed for correct invocation.

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%; all three parameters (customerId, userListId, customerData) are already described in the schema. The tool description adds no additional meaning beyond reiterating the upload operation. Baseline 3 is appropriate when the schema fully documents parameters.

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 action (upload), the object (customer data), and the destination (customer match list). It is specific enough to distinguish from sibling tools like create_customer_match_list (which creates the list) and import_offline_conversions (which handles conversion data).

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. For example, it does not mention that the customer match list must already exist (via create_customer_match_list) or clarify whether this is for appending vs. replacing data. The description gives no contextual usage cues.

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