OpenPanel: Track page view

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description does not need to say the call writes. But it discloses nothing beyond that: no mention of deduplication, attribution or session behavior, nor what client_ip, profile_id or user_agent do. It also gives no rate-limit or side-effect context, which matters for a non-idempotent tracking call.

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?

Short and front-loaded, with the verb leading the sentence, so nothing is padded. But the single sentence is too thin for an eight-parameter call, and the unexplained "[UNIFIED]" prefix costs clarity without adding meaning.

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?

For a non-idempotent event-submission tool with eight parameters, zero schema coverage, and no output schema, one sentence cannot cover what the caller needs. It omits required-field expectations, parameter meanings, and any note on duplicate submissions or attribution, so the agent can only guess at 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?

Eight parameters with 0% schema description coverage and no output schema, so the description carries the full explanatory burden. It names only URL and referrer, leaving site, path, title, client_ip, profile_id, properties and user_agent completely undocumented. The agent cannot tell required fields from optional ones or what format path expects.

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: "Track a page view event". That is enough to distinguish it from non-tracking siblings, but the bracketed "[UNIFIED]" tag is unexplained noise and the phrase "with URL and referrer information" only hints at scope. It does not differentiate this from openpanel_track_event or openpanel_track_screen_view.

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 at all about when to use this rather than openpanel_track_event or openpanel_track_screen_view, and no prerequisites such as whether the site must already exist or whether an API key or client is required. The agent must infer the choice from the name alone.

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