OpenPanel: Export profile data

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

Annotations already declare readOnlyHint=true, and the description adds real value beyond them by naming the return contents (events plus profile data) and the auth requirement ("read" or "root" mode client). It says nothing about export size limits, async/synchronous behavior, or whether profile data is redacted, which matters for a bulk export tool.

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?

Three short sentences, front-loaded with the action, then the return contents, then the prerequisite. Nothing is redundant, though the bracketed "[UNIFIED]" tag is noise that consumes attention without information.

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?

With no output schema, the description must carry return-shape information; it only says "events and profile data" and hints at json formatting via the parameter, leaving result structure and volume unspecified. The auth prerequisite is covered, but a four-parameter export tool deserves more about what comes back.

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%, so the description carries the full burden and fails: none of site, project_id, profile_id, or format is explained. The format parameter with default "json" has an unenumerated anyOf type, and the description never states what values it accepts or whether it changes the return shape.

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 concrete verb+resource ("Export all data for a user profile") and adds the GDPR portability intent, which tells an agent the scope is the whole profile rather than a slice. It is distinguishable from siblings like openpanel_get_profile_events, though it never names them, and the "[UNIFIED]" prefix adds no meaning.

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 GDPR data-portability framing implies the when-to-use context (a user requests a copy of their data), but there is no explicit when-not guidance and no pointer to openpanel_export_events or openpanel_get_profile_events for narrower exports. The agent must infer the boundary itself.

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