OpenPanel: Get profile sessions

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the auth/mode requirement and the fact that it goes through the Export API, which signals heavier or differently-shaped data retrieval. It does not disclose pagination behavior, whether the default limit of 20 truncates results, or what a session record contains.

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 short sentences, front-loaded with the action and scope, followed by the access constraint. The '[UNIFIED]' prefix is mildly noisy but does convey that this is the canonical variant; no sentence is wasted.

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, no parameter descriptions, and three required identifiers, the definition should say more about what a session is and how limit/site/project_id behave. An agent can attempt the call but cannot predict the response shape or whether results are truncated.

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 4 parameters, so the description carries the full burden and largely fails it: only profile_id is implicitly explained ('specific user profile'). Site, project_id, and limit (default 20) are undocumented in both schema and description, leaving three required/behavior-affecting parameters opaque.

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?

Names a specific verb and resource ('Get sessions') scoped to 'a specific user profile' and states the transport ('via Export API'). The resource 'sessions' is inherently distinguishable from siblings like openpanel_get_profile_events or openpanel_export_profile_data, though the description never explicitly contrasts them.

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?

Adds a concrete prerequisite ('Requires read or root mode client'), which tells the agent whether the call can succeed at all. However, it gives no guidance on when to pick sessions over profile events or a full profile export, leaving the choice to inference from the name.

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