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

Even though annotations already mark it as read-only and idempotent, the description adds crucial interpretive guardrails: fact classes are explained, marks are not impairments, maturity changes are not amendments, and non-accrual/default are never inferred. This goes well beyond the annotations and prevents misreading of sensitive fields.

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 dense and run-on, but every clause contributes meaningful constraints or clarifications. It is front-loaded with the main return scope before moving into fact-class semantics and caveats. Slight structural improvement would be easier scanning as separate sentences.

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?

With no output schema, the description carries the full burden of conveying the shape and semantics of results. It specifies every data category, the meaning of fact classes, and explicit boundary conditions. An agent has enough context to call this tool and interpret its output 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?

The only parameter, dfx_id, is fully documented in the schema with format and provenance guidance. The description adds no additional parameter semantics, but since schema description coverage is 100%, the baseline of 3 is appropriate.

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 precisely enumerates what the tool returns: the borrower group, facilities, BDC pieces, tape, sponsor attributions, and events. It clearly distinguishes this from sibling tools like get_borrower_facilities by signaling it is the full consolidated capital-structure view from BDC lenders' perspective.

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 title and description make it clear this is for the comprehensive borrower capital structure as BDC lenders see it, including derived, carried, and inferred data. It does not explicitly name alternatives or say when not to use it, but the scope is strongly implied by the exhaustive component list.

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