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

With no annotations, the description carries the full burden. It adds meaningful behavioral context by describing the data content and explaining that include_lenders adds syndicate allocations. It stops short of explicitly addressing read-only status, pagination, or output format, but the static 'loan book' phrasing and safe data-query nature are reasonably conveyed.

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 with dense, relevant information. The first sentence front-loads the core resource and fields; the second provides positioning and usage. Every clause earns its place, with no filler or repetition.

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 absence of an output schema, the description does a good job telling the agent what data to expect (facility-level details, covenants, optional lender allocations). It also supplies context about how it fits with the bond tape. Minor gaps exist around API-specific behaviors like limit semantics and possible empty results, but overall it is substantially complete.

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 coverage is low (only ticker has a tautological description). The description compensates by clarifying that ticker is a borrower ticker and explaining that include_lenders adds recent-facility allocations. However, the limit parameter is left entirely undocumented, meaning the agent receives no semantic guidance for it.

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 identifies the resource as a syndicated loan book for a single borrower, enumerating the specific data fields (facility size, type, maturity, security/seniority, spreads, covenants). It distinguishes itself from sibling credit tools by explicitly positioning as a private-credit complement to the TRACE bond tape, making its scope unambiguous.

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 explicitly states when to use this tool ('call for leverage, facility or covenant questions') and contrasts it with the bond tape (tengu_v3_credit_bonds). It also specifies the matching mechanism ('match on borrower ticker'), giving the agent clear criteria for tool selection.

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