openpanel_search_profiles

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

With no annotations provided, the description carries full disclosure burden but fails to specify if results are paginated, what data is returned, available operator types (only default 'contains' is implied), or rate limiting concerns. 'Search' implies read-only but this is notexplicitly confirmed.

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?

Extremely concise at one sentence. The '[UNIFIED]' tag appears to be metadata noise that doesn't aid clarity, but the description isn't bloated. However, extreme brevity leaves critical gaps for a 6-parameter search operation.

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 complex search tool with 6 parameters (including filtering and pagination), zero schema descriptions, no output schema, and no annotations, the description is insufficient. It fails to explain the search capabilities, expected property types, or result format needed for effective 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 6 parameters, the description inadequately compensates. It only implicitly references 'property' and 'value' parameters. It completely omits context for 'site', 'project_id', 'operator' (what operators exist?), and 'limit' (max value? pagination behavior?).

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 states a clear verb ('Search'), resource ('user profiles'), and mechanism ('by property value'). This distinguishes it from siblings like openpanel_list_profiles (unfiltered enumeration) and openpanel_get_profile (direct retrieval by ID). The '[UNIFIED]' prefix is implementation noise but doesn't obscure the core purpose.

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?

No guidance provided on when to use this tool versus openpanel_list_profiles or openpanel_get_profile. No prerequisites mentioned for the required site and project_id parameters, nor any mention of search syntax requirements.

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