Search Contacts

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral detail beyond annotations: filter type mismatches return 400, and property identifiers follow formats like `contact_companyName` or `contactPerson_email`.

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 short and front-loaded, with the core search purpose stated first and the filter caveat immediately after. The initial 'Search Contacts.' line repeats the title and is slightly redundant, but the overall structure is efficient.

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 search tool with a complex nested filter schema, the description covers the critical filter-type matching rule and property identifier format, and points to help tools. It does not mention pagination or the saved-filter versus inline-filter choice, but those are documented in the schema body description.

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 description coverage is high, so the baseline is 3. The description adds meaningful semantics by explaining that `condition.type` must match the selected property's type and by giving example property identifiers, pointing agents to `list_properties` and `get_api_guide` for supported formats.

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 specific verb and resource: searching contacts with flexible filters and sorting. It clearly says what the tool does, though it does not explicitly differentiate from the sibling `list_contacts` tool.

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 phrase 'using flexible filters and sorting' implies this tool is for filtered or sorted contact retrieval, but the description does not explicitly say when to use it instead of `list_contacts` or when to choose saved filters versus inline filter groups.

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