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

Annotations only declare readOnlyHint=true, so the description carries the behavioral load and does so well: default/hard caps on both params, the default min_holders, the parser mis-ingest filtering and the `borrower_filters` flag reporting whether it ran, data freshness ('latest filings'), and provenance ('SEC EDGAR BDC schedules of investments (Oxford Ledge parse); FREE').

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?

Dense but front-loaded: purpose and ranking come first, then return shape, then caps and caveats. Every clause carries information, though the packed semicolon-run format is heavier than ideal for quick scanning.

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 compensates by documenting the return envelope {summary, count, borrowers} and per-row fields including the borrower_norm key and unit conventions ('whole USD, latest filings'). Combined with caps, defaults, and the data source, an agent has everything needed to call and interpret this tool.

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 100%, and the description's param information (limit default 25/hard 100, min_holders default 2/max 50, 'lenders a borrower must appear in') restates what the schema already declares. It adds marginal value through the holder-count ranking semantics but does not extend the parameters meaningfully, so the baseline 3 applies.

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?

States a specific verb+resource (rank private-credit borrowers syndicated across the most BDCs) and self-identifies as 'the entrypoint for the BDC/private-credit category'. The ranking key (holder_count_active, then holder_count, then exposure) is spelled out, so an agent can distinguish it from sibling borrower tools like ol_bdc_common_borrowers or search_bdc_borrower without opening schemas.

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?

It explicitly routes the agent downstream: 'Feed a borrower_norm into ol_bdc_borrower_dispersion for cross-lender pricing', and states the entrypoint role for the BDC category. It lacks explicit when-not-to-use guidance (e.g., versus ol_bdc_common_borrowers or search_bdc_borrower), which keeps it short of a 5.

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