openpanel_get_profile_events

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to clarify what constitutes an 'event' in this context, whether results are paginated (despite the limit parameter), or the return format. It implies read-only safety but does not explicitly confirm it.

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?

Single sentence is front-loaded, but the '[UNIFIED]' tag constitutes noise that does not earn its place. The brevity would be acceptable if it carried more semantic weight, but as is, it under-specifies.

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 tool with 5 parameters (3 required), 0% schema coverage, and no output schema, the description is inadequate. It omits necessary context for the optional parameters (event, limit) and fails to distinguish this from related profile-inspection tools.

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%, yet the description provides no compensatory information for any of the 5 parameters (site, project_id, profile_id, event, limit). Critical semantics like what 'site' refers to, what the 'event' filter accepts, or default behaviors are entirely undocumented.

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 the specific action (Get) and resource (events) for a target (user profile), providing clear verb-resource-scope. However, the '[UNIFIED]' prefix appears to be an internal metadata artifact that leaks into the user-facing description, slightly diminishing clarity.

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 versus siblings like 'openpanel_get_profile_sessions' or 'openpanel_get_profile', nor does it mention prerequisites for the required identifiers (site, project_id, profile_id).

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