Datamanager.Conversions.Upload

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

With no annotations, the description carries the full burden, and it does contribute two real behavioral constraints: identifiers must be SHA-256 hashed/normalized and EEA uploads require consent. But the most important trait for a mutation tool — the "guarded" confirm flow implied by the optional `confirm` parameter (likely a two-step preview/token gate) — is never explained, nor is irreversibility or rate limiting.

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?

Two compact sentences with the core operation front-loaded and no filler. It is efficiently written, though the terseness is part of the reason key behaviors go undisclosed.

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?

Output schema exists, so return values need no explanation, and the description covers the two most error-prone inputs (hashing and EEA consent). Given a 4-parameter mutation with an unexplained confirm gate and no annotations, however, an agent still lacks what it needs to invoke the tool correctly on the first try.

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 0% across four parameters including nested objects, so the description must compensate and largely does not. It implies what belongs inside `conversions` (hashed identifiers) and `consent` (EEA), but `destination_id` and especially the optional `confirm` parameter are left entirely unexplained.

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?

States a specific verb and resource ("Upload offline + enhanced conversions") that an agent can map to a concrete operation. It does not, however, differentiate itself from the sibling sa360.conversion.upload or datamanager.audience.upload_members, so the agent must infer which upload path applies.

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 when-to-use guidance, no prerequisites, no mention of alternatives such as sa360.conversion.upload or datamanager.request_status for checking an upload. The parenthetical "(guarded)" hints at a gating condition without stating when the guard applies or how to satisfy it.

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