openpanel_identify_user

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

No annotations are provided, so the description carries the full burden. It does not disclose whether this creates a new profile or updates existing ones, whether it is idempotent, what happens to existing properties not provided in the call, or any rate limiting considerations.

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 description is appropriately brief with two sentences. However, the '[UNIFIED]' prefix appears to be internal metadata leakage rather than helpful context for the agent.

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 the high parameter count (8) with zero schema documentation and no output schema, the description is insufficient. It omits critical details about parameter semantics, required fields, and expected behavior that would be necessary for correct invocation.

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 8 parameters, the description fails to compensate adequately. While it loosely references 'profile properties' (hinting at the `properties` parameter), it does not explain the required `site` or `profile_id` parameters, the expected format for `properties` (JSON string?), or the purpose of `client_ip` and `user_agent`.

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?

The description clearly states the tool 'Identify a user and set their profile properties' and explains the goal is to 'associate events with users.' However, it fails to distinguish from the sibling tool `openpanel_set_user_properties`, which appears to have overlapping functionality.

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 description provides implied usage ('Use this to associate events with users') but lacks explicit guidance on when to use this versus `openpanel_set_user_properties`, when identification should occur relative to event tracking, or any prerequisites like needing an existing profile.

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