isw_validate_customer

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

With no annotations, the description carries full burden for behavioral disclosure. It states 'validate' but does not specify if this is a read-only check or has side effects, what constitutes success/failure, or any authorization requirements. The agent is left guessing the tool's behavior.

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 sentence, concise and front-loaded. However, the brief format sacrifices necessary detail that could have been included without losing conciseness.

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?

Given no output schema and no annotations, the description is the only guide. It lacks details on return values, error handling, and how to distinguish identifier types. This incompleteness is problematic for a tool that likely feeds into bill payment workflows.

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. It mentions 'customer account, meter, or phone number' but does not clarify how these map to the 'customerId' parameter or what the 'extra' object is for. The ambiguity about identifier types hinders correct invocation.

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 uses the specific verb 'validate' and identifies the resource as 'a customer account, meter, or phone number for a biller.' This clearly states the tool's function but does not differentiate it from sibling tools like 'isw_validate_card' or 'isw_get_customer_demographics,' which serve distinct purposes.

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?

No guidance is provided on when to use this tool versus alternatives. Among sibling tools, there are many related validation and enquiry tools (e.g., isw_fintech_validate_*), but the description offers no context for selection or prerequisites.

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