ghl_contact_search_advanced

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

The description states 'Search' implying a read-only operation, yet annotations set readOnlyHint: false, contradicting the described behavior. Additionally, the OAuth scope 'contacts.readonly' further suggests read-only, conflicting with readOnlyHint. This contradiction undermines transparency.

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 verbose and front-loads a technical note about the spec gap, burying the actual purpose and usage details. Essential information like 'Search Contacts' only appears mid-text, reducing clarity and readability.

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?

The description provides an external documentation link, endpoint details, and OAuth scopes, which are helpful. However, it lacks practical guidance on how to construct queries, expected output (no output schema), and explicit usage prerequisites, leaving gaps for complex advanced search functionality.

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?

The input schema for 'body' is empty, but the description compensates by explaining the schema gap, linking to external documentation for real field names, and noting that the body accepts arbitrary JSON for advanced filters. This adds significant meaning beyond the schema's minimal description.

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 'Search contacts based on combinations of advanced filters,' indicating a specific verb (search) and resource (contacts) with advanced filtering capability. However, it does not explicitly differentiate from sibling tools like ghl_contact_list or potential basic search tools, missing an opportunity to clarify its unique value.

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 such as ghl_contact_list or other search tools. It mentions 'advanced filters' but does not elaborate on scenarios where this tool is preferred, leaving the agent without clear usage context.

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