openpanel_get_profile_sessions

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

No annotations are provided, so the description carries full burden of behavioral disclosure. While 'Get' implies read-only, the description fails to specify pagination behavior (despite the limit parameter), what data fields are returned in sessions, rate limits, or whether sessions include sensitive data.

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 core sentence is appropriately brief and front-loaded, but the '[UNIFIED]' prefix wastes space with implementation metadata that doesn't help the AI agent. No sentences earn their place beyond the basic definition.

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?

Given 4 parameters with zero schema descriptions, no annotations, and no output schema, the description is grossly inadequate. It fails to explain critical parameters (site vs project_id distinction) or what the session data structure looks like.

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 4 parameters, the description must compensate but provides zero guidance. No explanation of the relationship between 'site' and 'project_id', valid formats for 'profile_id', or that 'limit' defaults to 20 and controls result pagination.

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 basic verb and resource ('Get sessions for a specific user profile'), but the '[UNIFIED]' prefix is noisy metadata that adds no value. Distinguishes from siblings like openpanel_get_profile_events by mentioning 'sessions', though it doesn't explain what constitutes a session vs other profile data.

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?

Provides no guidance on when to use this tool versus alternatives like openpanel_get_profile_events or openpanel_get_profile. Does not mention prerequisites (e.g., needing a profile_id from openpanel_get_profile first) or typical use cases.

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