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

Annotations only declare readOnlyHint=true, and the description adds substantial context: coverage-limited scope, exclusion of wound-down issuers, that holdingCount/totalFairValue are Oxford Ledge's parse rather than filer-published, and a warning to read fairValueBasis and fairValueGap before trusting totalFairValue because an under-counting parse understates the book. This is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with purpose and scope before the field list and caveats. The enumerated return fields are dense but each carries real information; slightly long, though little is expendable given the warning content.

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?

There is no output schema, so the description carries the full burden of explaining the return shape — {bdcs, count} with per-BDC fields — and it does, plus points to tool_notes for caveats. Nothing an agent needs to interpret the response 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?

Zero parameters, so the baseline is 4. The description reinforces this with 'No arguments,' leaving no ambiguity about invocation.

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 and resource ('Roster of the ACTIVE BDCs tracked by Oxford Ledge'), gives the ordering ('sorted by portfolio size'), and explicitly scopes it as 'our coverage, not the whole BDC universe.' An agent can immediately tell this apart from sibling tools like search_bdc_borrower.

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?

Explicitly says wound-down issuers are 'excluded by design' and names the borrower-keyed counterpart search_bdc_borrower, which routes the agent to the alternative. It stops short of a full when/when-not statement, so it is clear rather than exhaustive.

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