Search Customers

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the tool is safe. The description adds that filtering is client-side and supports partial matches, which provides additional context but does not go beyond what the annotations convey about safety. It does not contradict annotations.

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 a single sentence that is front-loaded with purpose, covering all key aspects without waste. It is highly concise and effective.

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 description addresses the main search modes and client-side filtering. However, it does not explain pagination behavior (page, page_size) or the implications of client-side filtering (e.g., whether all results are fetched first). Given the schema already documents parameters, the description is largely complete for a search tool but could mention pagination or that all parameters are optional.

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 all five parameters have descriptions in the input schema. The description only summarizes the search criteria without adding new meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 verb 'search' and resource 'customers', specifying three search types (identification, name, type) and mentioning client-side filtering for partial matches. It distinguishes from sibling tools like siigo_get_customers and siigo_get_customer which likely return all customers or a single customer without partial match search.

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 usage when needing to find customers by partial match on identification, name, or type, but it does not explicitly state when to use this tool versus alternatives like siigo_get_customers or siigo_get_customer. No exclusions or alternative recommendations are provided.

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