customers__get_customer_by_card_number

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds a valuable behavioral trait beyond annotations: it is a wrapper with no own throttling but consumes the underlying API quota, and advises caching the result in the dialog. This gives actionable rate-limit and caching context.

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?

Two sentences with no filler. The first states the core function, the second delivers the behavioral warning and caching recommendation. Every word earns 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 simple two-parameter read-only lookup, the description covers the purpose and a key behavioral constraint, but it omits parameter semantics and any indication of return value structure. Since no output schema exists, the agent is left to infer what the returned customer object looks like.

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 0%, so the description must compensate for missing parameter details. It does not: card_number is only labeled as the loyalty card number (redundant with the property name), and organization_id is not explained at all. No format, constraints, or purpose are added.

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?

Description states a specific action: 'Получить клиента по номеру карты лояльности' (get customer by loyalty card number). This clearly identifies the verb, resource, and lookup key, distinguishing it from siblings like get_customer_by_phone or get_customer_by_id.

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 does not provide explicit when-to-use or alternative guidance. The usage context is implied by the tool name and purpose statement, but no direction is given for choosing between this and sibling customer lookup tools.

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