search_contacts

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

No annotations are provided, so the description carries full behavioral burden. It discloses that only the first page of results is returned, which is useful. However, it doesn't explicitly state read-only status, authentication needs, or result ordering. The mention of 'quick' is vague. The pagination behavior is a positive addition but not comprehensive.

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 two short sentences, front-loaded with the purpose. Every word contributes: 'Quick search' conveys the action and style, and 'first page' adds a key behavioral detail. No fluff or redundancy.

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 tool is simple with one parameter and no output schema. The description notes pagination but doesn't explain the return structure or how to access subsequent pages. It's adequate but lacks detail on result format, which would be needed absent an output schema or annotation support.

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 100% for the single query parameter, so the baseline is 3. The description reinforces that the query matches name, email, and company, which mirrors the schema's explanation. It adds no additional syntax or formatting details beyond what the schema provides.

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 the tool's purpose: 'Quick search across contacts by name, email, or company.' It specifies the resource (contacts) and the search fields, distinguishing it from list_contacts (listing all) and get_contact (fetching by ID).

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 implies use for searching contacts by keyword but does not explicitly mention when not to use it or suggest alternatives like list_contacts for browsing or get_contact for a specific known contact. The context 'quick search' hints at its niche but lacks explicit exclusionary guidance.

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