get_lender

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

No annotations are provided, so the description carries the transparency burden. It discloses the data source (US SBA, public domain), the quarterly history behavior, and the dependency between the two optional filters. This adds meaningful behavioral context beyond the schema, though it doesn't specify behavior for invalid IDs or period formats.

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, front-loaded with the primary purpose, and every clause adds value. The second sentence efficiently covers parameters, constraints, and source attribution without redundant detail.

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 the tool's simple get-by-id nature with optional filters, and the presence of an output schema, the description is complete. It covers what the tool does, the data source, filter semantics, and required dependencies, leaving no critical gaps for an agent to invoke it correctly.

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%, but the description fully explains all parameters: lender_id identifies the single lender, and from_period/to_period define the quarterly range with format 'YYYY-Qq' and the constraint that they must be used together or omitted. This goes well beyond the schema's basic type and title information.

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's purpose: 'Get details and quarterly history for a single SBA 7(a) lender by lender_id.' This is a specific verb+resource+identifier, and it naturally distinguishes from siblings like get_lenders (plural) or get_county_lending.

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 clear parameter usage context: 'Optional from_period/to_period filters the quarterly history range... Both are required together for a range; omit both for full history.' It explains when to use the filters, but does not explicitly mention when to use this tool versus alternatives such as get_lenders.

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