find_itin_lenders

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

Annotations already declare readOnlyHint and destructiveHint=false, so the safety profile is known. The description adds meaningful behavioral context by stating that every entry includes verification status, citation URLs, and dates, which goes beyond the structured fields. No contradictions with 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?

Two concise sentences with the core action front-loaded and a key behavioral detail in the second sentence. Every word earns its place; no redundant or vague phrasing.

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 3-parameter, no-output-schema tool, the description covers the main purpose and the verification feature. Annotation openWorldHint covers the non-exhaustive nature, and schema documents state and lang. While the exact output structure is not fully specified, the description provides enough context for an agent to understand what to expect.

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 67% with only lang and state described. The description adds semantic value by connecting 'loan or card type' to the loan_type parameter and mentioning optional state filtering, helping disambiguate the purpose of these parameters. This partially compensates for the missing loan_type description.

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 lists institutions accepting ITIN applicants for a loan or card type, with optional state filtering. It uses a specific verb ('List') and resource ('institutions that accept ITIN applicants'), and the scope is distinct from siblings like get_lender_details, which focuses on individual lender details.

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 implies usage for finding ITIN-accepting institutions but provides no explicit guidance on when to use this tool versus alternatives. It does not mention get_lender_details or other sibling tools as alternatives, nor does it state when not to use the tool. The context is implied rather than explicit.

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