OpenPanel: Get profile events

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds genuinely new context by naming the backing API (Export API) and the required client mode, which affects whether a call will succeed. It does not cover result format, pagination, or whether limit truncation occurs.

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?

Two compact sentences with no filler, and the operation is front-loaded before the requirement. It is tight, though tightness here shades into under-specification rather than elegant economy.

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 and 0% schema coverage on five parameters, the description should explain site vs project_id, what the event filter does, and how limit behaves. None of that is present, leaving real ambiguity for a tool that requires three identifiers to call 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?

Schema description coverage is 0% across five parameters, so the description must carry the burden and largely does not. It hints that profile_id identifies the user, but site, project_id, event (a filter?), and limit (pagination?) are left entirely undefined in both schema and description.

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: 'Get events for a specific user profile via Export API.' This distinguishes it from openpanel_get_profile_sessions (sessions, not events) and from general exports. It does not name a sibling outright, so a 4 rather than a 5.

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 guidance is the prerequisite 'Requires read or root mode client,' which tells the agent what kind of client must be configured. There is no statement of when to prefer this over openpanel_export_events or openpanel_get_profile_sessions, so selection must be inferred from the tool name.

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