customers__get_customer_by_card_track

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that the tool is a thin wrapper with no throttling of its own and that calls consume quota from the underlying API, recommending caching in the dialog. This is valuable behavioral context beyond the annotations.

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 sentences long, with the primary purpose first and the operational note second. No unnecessary words; each sentence adds relevant information.

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 read-only lookup with two parameters and no output schema, the description covers the purpose and one operational caveat (quota usage). However, it does not describe the return payload or clarify the precise format of card_track, leaving some gaps for an agent that needs to parse the result.

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 schema has no descriptions and the description does not explain the parameters either. The names 'card_track' and 'organization_id' are somewhat self-explanatory, but the expected format of 'card_track' (e.g., raw magnetic stripe data, track 1/2/3) is not specified, so the description does little to compensate for the 0% schema coverage.

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 states a clear action: retrieving a customer by the card's magnetic stripe. It is distinguishable from sibling tools that look up by phone, id, email, or card number, though the difference from 'by_card_number' is not explicitly spelled out.

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 provides no guidance on when to choose this tool over alternatives like customers__get_customer_by_card_number, by_phone, or by_id. It only gives operational advice about caching and quota usage, which does not help with tool selection.

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