search_customers

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

With no annotations provided, the description carries the full burden of disclosure, but it only states the action without revealing any behavioral traits such as return format, pagination behavior, ordering, or side effects. It adds no information beyond the tool name, essentially being a tautology.

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 extremely brief and front-loaded, but it is under-specified rather than appropriately concise. It repeats the tool name and provides zero useful information, which fails the requirement that every sentence earn its place.

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?

For a search tool with two optional parameters and no output schema, the description is insufficient. It does not explain what the results look like, whether unfiltered search is allowed, or any other contextual detail needed for an agent to invoke it correctly. The simplicity of the tool does not excuse the lack of essential information.

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?

The input schema provides full descriptions for both parameters (email and limit), achieving 100% schema description coverage. The description itself offers no additional parameter semantics, but since the schema is self-sufficient, the baseline score of 3 applies.

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 'Search for customers' is essentially a restatement of the tool name 'search_customers' with spaces added. It does not add any specificity beyond the name and fails to distinguish this tool from siblings like get_customer or search_payments.

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?

There is no guidance on when to use this tool compared to alternatives like get_customer or create_customer. The description lacks any contextual cues about appropriate usage scenarios, required prerequisites, or intended use cases.

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