contacts_search_contacts_advanced

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral detail such as pagination, filtering constraints, or response characteristics. It does not contradict annotations but contributes nothing beyond them.

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 only two words, which is under-specced rather than concise. While it is front-loaded, it lacks any substantive information. Every word earns its place, but there are almost no words, so the structure is too sparse to be useful.

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 an advanced search tool with a single opaque body parameter and no output schema, the description is completely inadequate. An agent has no idea what filters are supported, how to construct the request body, or what results to expect. The description fails to provide even minimal context.

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 coverage is 100% for the single 'body' parameter, which is described as 'Request body as defined by the HighLevel API.' The description itself adds no parameter explanation, but the baseline is 3 because the schema already covers the parameter. There is no enhancement from the 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 'Search Contacts' states a verb and resource but is extremely vague. It does not explain what makes this 'advanced' or how it differs from sibling tools like contacts_get_contacts or contacts_search_contact. The purpose is clear in the broadest sense but lacks the specificity needed for an agent to distinguish it.

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?

There is no guidance on when to use this tool versus alternatives. No context about use cases, prerequisites, or why 'advanced' search would be preferred over other contact search tools. The description provides zero orientation.

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