openpanel_get_profile

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only implies a read-only operation via the verb 'Get' but fails to disclose error conditions (e.g., profile not found), rate limits, caching behavior, or what 'detailed information' specifically includes.

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 and front-loaded with the action. However, the '[UNIFIED]' prefix appears to be metadata cruft that adds no value to the agent's understanding.

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 three undocumented required parameters and no output schema, the description is insufficiently complete. It lacks necessary details about parameter meanings, return value structure, and behavioral characteristics that would help an agent invoke the tool 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?

With 0% schema description coverage for all three required parameters (site, project_id, profile_id), the description fails to compensate by explaining parameter semantics, valid formats, or examples. It only indirectly hints at profile_id through the phrase 'specific user profile'.

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 uses a clear verb ('Get') and resource ('user profile') and distinguishes itself from sibling tools like 'openpanel_list_profiles' by specifying 'specific' (implying single-item retrieval by ID) and from 'openpanel_get_profile_events/sessions' by targeting the profile information itself rather than sub-resources. However, it does not explicitly name sibling alternatives.

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 no guidance on when to use this tool versus alternatives (e.g., when you have a profile_id vs. when you need to search), nor does it mention prerequisites like needing valid project_id or site credentials first.

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