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

Annotations already declare a safe read-only, idempotent, non-destructive operation, and the description adds substantial behavioral context beyond them: plan-gated access, first-5-row truncation, locked count/by_type behavior, withheld contact and decision-maker data, and entitlement/locked disclosure. It does not contradict any annotation.

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 long but front-loads the core retrieval scope and field list before access details. The access and entitlement sentences are dense but earn their place for a tool with real gating behavior; the promotional plan URL is the only slightly extraneous element.

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 covers the returned fields, paging behavior, default debt-only filtering, access restrictions, and withheld-data disclosure in entitlement/locked. For a complex, gated BDC portfolio tool, this gives an agent enough to invoke and interpret 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 only 50%, so the description must compensate. It adds useful meaning for as_of (latest quarter end), include_equity (debt only by default), and paging (25 rows), but it does not explain the sort parameter's meaning or the cursor beyond the schema's own description, leaving some gaps.

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 retrieval verb and resource: every position a BDC tagged at one quarter end, with the exact fields returned. It distinguishes this from sibling tools by centering on one BDC's schedule of investments rather than sponsors, borrowers, or search endpoints.

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 implies when to use the tool by describing its scope and default debt-only behavior, but it never names when to use it instead of alternatives such as search_private_credit or get_borrower_capital_structure. No explicit exclusions or routing guidance are provided.

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