openpanel_track_event

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

No annotations provided, so description carries full burden. It mentions 'track' but fails to disclose side effects (creates records, updates profiles), rate limits, idempotency behavior, or what happens when optional parameters like profile_id are omitted. No mention of timestamp format requirements or client_ip usage.

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 brief (two sentences), but the '[UNIFIED]' prefix appears to be metadata noise leaking into the description rather than useful information for the agent. Otherwise efficiently structured.

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?

Inadequate for a 7-parameter analytics tool with no output schema and no annotations. Missing critical context: authentication requirements, rate limiting, response format, whether events are processed synchronously, and semantics of the 'site' parameter (which is required but unexplained).

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?

With 0% schema description coverage across 7 parameters, the description fails to compensate adequately. It only vaguely references 'properties' without explaining the other 6 parameters (site, name, profile_id, timestamp, client_ip, user_agent). No explanation of what 'site' refers to (ID vs domain) or timestamp format.

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 tool tracks 'custom events with properties' for analytics, using specific verb+resource. It implicitly distinguishes from siblings like openpanel_track_page_view (specific event types) by emphasizing 'custom', though it could explicitly contrast with batch tracking or identify operations.

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 provided on when to use this tool versus alternatives like openpanel_track_batch (for bulk events), openpanel_track_page_view (for page views), or openpanel_identify_user (for user identification). No prerequisites or conditions mentioned despite required 'site' and 'name' parameters.

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