import_offline_conversions

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

No annotations are provided, so the description carries full burden. It implies a write operation ('upload') but fails to disclose any behavioral traits such as idempotency, validation requirements, error conditions, or whether it appends or replaces data. Minimal info beyond the action itself.

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 extremely concise but may border on under-specification. It is a single clause that efficiently states the high-level purpose, but lacks any structured details like prerequisites or usage notes. It earns its place but does not go beyond a minimal phrase.

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 the tool has a nested conversions array and sits among many conversion-related tools, the description is too sparse. It does not mention expected data format, relationship to conversion actions, or return behavior. No output schema or annotations exist to compensate, leaving significant gaps for an agent to operate correctly.

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?

The input schema covers 100% of parameters with descriptions for customerId and conversions, including nested fields. The description adds no additional parameter semantics, so the schema already does the heavy lifting. Baseline of 3 is appropriate because it neither adds nor detracts from schema documentation.

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 identifies the tool's action ('Upload') and target ('offline conversion data'), which is a specific resource. It distinguishes from read-only or definitional siblings like get_conversions and create_conversion_action, though it does not explicitly name them. Lacks explicit scope beyond 'offline', but enough to infer the primary use case.

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, prerequisites, or typical scenarios. The description is just a single phrase with no context for decision-making. Does not mislead, but offers no direction.

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