OpenPanel: Track batch

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the safety profile is known and the description does not contradict it. However, the description adds nothing beyond that: it does not say events are ingested permanently and un-undoable, whether a partially accepted batch is possible, or that repeated identical batches will double-count (consistent with non-idempotent). For a destructive, non-idempotent write tool this leaves real behavioral questions unanswered.

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?

It is a single front-loaded sentence with no padding, which is structurally clean. The brevity is under-specification rather than true conciseness, and the bracketed "[UNIFIED]" tag is noise that does not help an agent.

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 a destructive batch write with four undocumented parameters, an untyped events array, and no output schema, the description is far too thin to let an agent call this correctly. It should at minimum describe the event object shape, batching constraints, and what a successful batch response confirms.

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, and the description only vaguely gestures at "events" without ever naming or defining site, events, client_ip, or user_agent. Critically, the events array has an empty item schema, so the agent gets no information anywhere about what an event object must contain — the description should have compensated and does not.

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 pairs a specific verb ("Track") with a resource ("multiple events") and a scope qualifier ("in a single request"), which implicitly separates it from the single-event sibling openpanel_track_event. The "[UNIFIED]" prefix is unexplained jargon that adds no meaning, and no sibling is named explicitly.

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?

The only usage signal is "for efficiency," which hints at batching but never states when to choose this tool over openpanel_track_event or the other track_* siblings. There is no guidance on limits, ordering, partial-failure behavior, or prerequisites such as valid site credentials.

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