Find Setell customers

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

The description declares the tool as read-only, aligning with annotations. It adds that each match returns jobCount, lifetimeValue, and lastJobAt, providing helpful behavioral detail beyond annotations. No contradictions.

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 three concise sentences: first defines purpose and search types, second lists return fields, third states requirements. No unnecessary words, well front-loaded.

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 3 parameters and no output schema, the description fully covers return fields, input requirements, and behavior. The information is sufficient for an agent to use the tool correctly.

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?

With 100% schema description coverage, the description still adds value by stating the requirement that at least one of email or name must be provided, and that limit defaults to 10. These constraints are not in the schema, so the description significantly enhances parameter understanding.

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 searches Setell customers by email (exact) or name (partial), lists return fields, and distinguishes from siblings like setell_find_jobs which search 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?

The description specifies that at least one of email or name is required, giving clear usage conditions. It does not, however, explicitly mention when not to use this tool or suggest alternatives, but the context of sibling tools implies it is the primary customer search.

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