search_contacts

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

No annotations provided, so description carries full burden. It discloses pagination and date format but does not explicitly state the tool is read-only or mention any side effects, authorization needs, or rate limits. Adequate but leaves room for improvement.

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?

Two concise sentences front-load the purpose, filter logic, and default behavior. Every sentence adds value with 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 the 12 optional parameters and existence of output schema, the description covers key search behaviors, pagination, date format, and filter logic. Lacks mention of a few filters (e.g., owner_id) but is generally complete 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 description coverage is 0%, so description must add meaning. It covers main parameter categories (name, email, company, date range) and implies limit but omits linkedin, contact_number, and owner_id. Provides useful context but incomplete.

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 'Search for contacts' with specific filterable fields (name, email, company, date range), distinguishing it from sibling search tools for other entities like candidates and jobs.

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?

Provides clear context: recommends at least one filter for targeted results, explains AND logic, and describes behavior without filters (paginated list of recent contacts). Lacks explicit exclusion of alternatives but is self-contained.

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