search_contacts

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

With no annotations, the description adds pagination details (startAfterId, startAfter) and mentions advanced filter endpoint, but does not explicitly state read-only nature, auth requirements, or rate limits. Partial disclosure.

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?

Single efficient sentence with key details front-loaded. No wasted words.

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 full schema coverage and no output schema, the description adequately covers search functionality and pagination. Could mention return format or typical fields, but sufficient for a search tool.

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%, so baseline is 3. Description summarizes search criteria but adds little beyond schema descriptions. No extra value for parameter interpretation.

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?

Clearly states verb (search) and resource (contacts), specifies searchable fields (name, email, phone, tag, advanced filters), distinguishing it from sibling tools like get_contact (single contact by ID) or list_* (list all).

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?

Describes how to search by various attributes and mentions advanced filters, giving clear usage context. However, lacks explicit when-not to use or alternatives like get_contact for known IDs.

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