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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses important caveats: principal is only the sum of BDC pieces and a lower bound, never the commitment, and lenders that file no schedule are omitted. It also signals historical holdings via 'quarters it held,' giving realistic expectations about data completeness.

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 but front-loaded with the core resource and contains no filler; every clause carries output or caveat information. It could be restructured into a clearer list, but it remains appropriately sized for the breadth of returned fields.

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 burden of explaining return values and does so thoroughly: facility fields, lender-level fields, historical quarters, credit manager, and principal semantics. The remaining defaults and id source are already supplied by the input schema, so nothing essential is missing.

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 schema documents dfx_id and held_only, covering two of three parameters, but the prose adds no parameter-level meaning and the limit parameter still has no description beyond its constraints. Since schema coverage is 67% rather than high, the description neither fully compensates nor needs to for the tool to be usable.

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 states a specific resource and perspective: every facility a borrower group has on the BDC tape, with the lender group on each. It clearly differentiates this from sibling entity-lookup and capital-structure tools by naming the data source and the lender-group detail.

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 scope is unambiguous: use this for a single borrower group's BDC-tape facilities and the lenders on each, including historical holders. It does not name alternatives or exclusions, but the context is clear enough for an agent to select it without being misled.

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