find_customer

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

There are no annotations and the description does not mention whether the operation is read-only, what it returns, or how it handles missing or ambiguous names. Since 'find' suggests a lookup, the lack of explicit side-effect or result information leaves uncertainty.

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 concise sentence that directly states the tool's purpose and key parameter. No unnecessary words or redundant details are present.

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 simple lookup tool, the description gives the essential action and input, but it omits output shape and error behavior. Without an output schema, more detail about what is returned would improve completeness.

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 only parameter, 'name', is mentioned in the description as the lookup key, so its basic purpose is clear. However, the description does not clarify exact matching, case sensitivity, or whether multiple matches are possible.

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 finds a customer using their name, which identifies both the action and the resource. It is distinguishable from sibling tools like get_customer and get_customer_balance, though 'find' is slightly less precise than 'get'.

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 phrase 'using their name' implies the intended use when a customer name is available. However, it does not explicitly contrast with get_customer or explain when to prefer this tool over alternatives.

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