search_customers

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the tool returns IDs and includes a '[tier: readonly-owner]' hint, but it doesn't explicitly mention that the search is read-only or explain pagination/limits. The includeData parameter's behavior is left to the schema, so transparency is limited.

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 concise sentences, front-loaded with the primary purpose and immediately pointing to the alternative. No unnecessary 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 16 parameters, no output schema, and no annotations, the description is far too brief. It doesn't explain the search semantics, parameter combinations, result limits, or the meaning of the read-only tier. The description covers only the most basic purpose and one sibling relationship.

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 only 25%, and the description adds no parameter-level semantics beyond the schema. It doesn't clarify how the filter parameters interact (e.g., AND/OR), what fields are searchable, or how to use extra_filters effectively. The description's brief mention of returning IDs doesn't help understand the parameters.

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 function: 'Search for customers and return matching IDs'. It also distinguishes itself from the sibling tool get_customers by explicitly directing users there for full records, providing a clear verb+resource+outcome.

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 gives explicit usage guidance: 'use get_customers to fetch full records' indicates when to use this search tool versus the alternative. It also provides the underlying endpoint mapping and tier, implying a read-only context.

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